I'm looking into deployment options for a desktop Java application that will run on Windows and Mac. I am currently looking at Web Start, but I have a few questions.
If I can create an executable jar file and the user can just double click it to start the app, why do I even need to use Web Start? Why not just stick the jar file up on the web server and let the user download that? What am I getting out of using Web Start?
My understanding is that Web Start comes when you install the JRE. But what happens if the user has not installed Java on their machine? Does it walk them through an installation process or do that have to go and download and install the JRE on their own?
See the Java Web Start Wiki page here at SO for most of your answers.
1) What am I getting out of using Web Start?
From the 2nd paragraph:
JWS provides many appealing features including, but not limited to
- splash screens
- desktop integration
- file associations
- automatic update (including lazy downloads and programmatic control of updates)
- partitioning of natives & other resource downloads by platform, architecture or Java version
- configuration of run-time environment (minimum J2SE version, run-time options, RAM etc.)
- easy management of common resources using extensions..
2) what happens if the user has not installed Java on their machine?
That is what the deployJava.js is for.
Java Rich Internet Applications Deployment Advice. Describes the
deployJava.jsscript designed to ensure a suitable minimum version of Java is installed before providing a link to a JWS app. or launching an applet.