JWS has always been good at updating Jars, but ..less so when updating the JNLP files themselves. A dynamically generated JNLP would typically lack an href
attribute to indicate to the Plug-In not to create a desktop shortcut.
On the other hand a work-around might be found in the IntegrationService
of the JNLP API. You might:
- Cache a copy of the last known JNLP in the
PersistenceService
. - At app. start-up, connect back to the server and explicitly read the JNLP.
- Compare it to the cached version.
- If changed, uninstall the desktop shortcut & relaunch the app.
- If not changed, and no desktop shortcut exists, prompt to install (new) desktop shortcut.
Steps 2 & 3 might be replaced by a simple check of the headers for the URL connection for the JNLP, if the server returns a valid 'last updated' time.