Java web app as desktop app, which frameworks should I choose?

Question

I need to make a web app that I would be able to install as a desktop application on a client PC (database, jetty+war, firefox/chrome/sth portable).

The application is a quite big search app (I MUST use Lucene). There are only few screens, some dependencies in search queue, etc.

Now I need help in choosing correct components. Application must be:

1. Light - minimalistic and user friendly frameworks (Java + JavaScript)
2. Efficient - working on old PCs and working fast
3. Developer Friendly - I would love to write it with pleasure ;)

So my questions are:

• Do you have any suggestions about choosing components?
• What frameworks, what obfuscator?
• Do you have any comments about making a web application a desktop application?
• What are the main risks?

Vogul

The First Rule of Program Obfuscation: Don't do it. The Second Rule of Program Obfuscation (for experts only!): Don't do it yet. – Cornemuse

Answer 1

Maybe you could take a look at Google's GWT. You can write Java code and it will then "compile" it to JavaScript. Using it feels like using a desktop app. Gmail, Google Wave,... have been created using this technology.

I think you don't even need a webserver, but the compiled result is pure JavaScript + static HML pages. If you then create a Chrome application shortcut it'll really look like a desktop app ;)

The only thing is that the learning curve will be a bit steep initially but if you're eager to learn, then it's really cool stuff and you can manage it easily.

Adler

Good point for new apps, but it's an already implemented application. About the server: you do need a web server for doing the real data stuff (but it can be anything). – Sussi

Answer 2

Many Java web apps distributed in this style are done so alongside a lightweight application server or web container such as Jetty or Tomcat.

When you click to start the application, this actually starts the container which internally hosts your application. (You're application can be packaged as a WAR internally.)

For lightweight databases, possibly look at SQLLite, HSQLDB, or Apache Derby. These can also be distributed alongside the application. Or maybe you can just collect database credentials as part of your install process and let the customer maintain their own database.

The arrangement you describe will involve work and custom scripting. You're going to the trouble of creating a thin, multi-user, web application and then throwing away the main benefit - the shared single instance. Customers, eh, who'd have them! :-)

Neckwear

Answer 3

Ha, I'm in the same boat. But I have many screens like normal web apps.

My suggestions is: 1, take web easy, no framework. Since there's little web pages, html+jquery+css is recommended; 2, lightweight database is not important. Because mysql does cost little memory, and it's user-friendly, large community. 3, So pay your attention on your search engine, and happy coding.

Testis