Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

9
  • I don't quite feel that Java Web Start is the answer here. Assume this is a largish application - close to an application "container" like Eclipse (the IDE) is, and like Firefox is. Commented Nov 20, 2008 at 16:06
  • 7
    Webstart is ok, but has lots of wierd issues. especially if you're installing multiple versions or the same version multiple times (which is not uncommon for developers/QA), and lots of things were you have to go to the cache viewer, etc. Commented Nov 20, 2008 at 18:25
  • 2
    Also, if you use webstart, the user can always turn on the java console, so be careful with whatever you're sending to System.out/err streams. Commented Nov 20, 2008 at 18:26
  • 3
    The problem with JWS is the security manager. It's further stricter than the normal one. Commented Dec 16, 2008 at 12:59
  • 1
    Be aware that Java Web Start traditionally has had a lot of caching problems. You can help a lot by ensuring that each version of each file you deploy has a unique URL (e.g. by embedding the version name or release number in the URL). Commented Feb 12, 2010 at 11:51