I had endless problems trying to get Web Start going so I made a simple alternative. You write your application, you drop it into a Tomcat folder, you put the URL in the browser page, the user can run it, or download it and run it later.
You know, reading the documentation for this... I'm still not convinced it's a better idea than Webstart.
Firstly, you don't have to buy a certificate from Verisign - there are alternatives. (I know for the apps I've been writing, I have been using such alternatives.) Second, yes, there are ways to do an install other than through their sandbox, but I think that the sandbox model - that you can download code without worrying about a potential attack, and being asked if it wants to do something beyond that little amount - is one of the draws of Java, not a detriment.
And, finally, I think your system actually takes a step back from the biggest benefit I've seen of webstart - namely, if there's an update to the application, with WebStart your application is automatically updated if you're launching online. It was designed to ease the deployment of clients and applications from a central server. Does your installer handle this?
Theodore Jonathan Casser
SCJP/SCSNI/SCBCD/SCWCD/SCDJWS/SCMAD/SCEA/MCTS/MCPD... and so many more letters than you can shake a stick at!
Joined: Aug 19, 2005
Welcome to the JavaRanch "Johnny Kewl":
I apologize if I am mistaken. However a quick look at the White Pages tells me that "Johnny Kewl" is a most likely a fictitious name. The naming policy at the JavaRanch bans obviously fictitious names. "Johnny Kewl" is perilously close to "Johnny Cool" which is also likely a fictitious name. Please adjust your display name to comply with the naming policy. Your cooperation is appreciated. [ April 17, 2007: Message edited by: Peer Reynders ]