Re: JARs versus Web-Start
On May 20, 9:39 am, r...@zedat.fu-berlin.de (Stefan Ram) wrote:
When one follows a web link to an executable JAR on a
webserver, it will be transferred via HTTP and then executed
(for example, under Windows, after Java was installed). ..
On Ubuntu Linux the user would be offered many options,
including 'save to disk' and 'open in archive manager'.
..The
operating system might ask the user for a confirmation and
then will run the JAR.
Many users do not know much about what a JAR is, so they
might not be able to appreciate the possibly enhanced
security of Applets or of Web-Start (is there any?)
Already covered.
So, in order to enable someone to start a Java-Application
via the Web, what might be some reasons to prefer one of
those means above the other (a link to an executable JAR
versus Web-Start)?
JWS provides..
- Easy ways to add extra APIs and entire extensions
(JOGL, Java3D etc.) to the application's run-time
classpath, including natives delivered specific for
the platform.
- Automatic update.
- Splash screens.
- Desk-top integration.
- APIs only available to JWS apps. like the
PersistenceService, the SingleInstanceService & the
ExtensionInsallerService that make some things very
much easier. E.G.s at <http://pscode.org/jws/api.html>
Note that Robot Chase app. mentioned by John could be
deployed sand-boxed, by using the PersistenceService.
- Fine-grained JRE versioning. For details see
<http://pscode.org/jws/version.html>
- ...
--
Andrew T.
pscode.org