JDK-6838214 : launch from desktop shortcuts of java web start application will not pick up JNLP update from server
  • Type: Bug
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: 6u14
  • Priority: P1
  • Status: Closed
  • Resolution: Fixed
  • OS: windows
  • CPU: x86
  • Submitted: 2009-05-06
  • Updated: 2013-01-10
  • Resolved: 2009-05-15
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6
6u14 b07Fixed
Related Reports
Relates :  
Description
create a  desktop shortcut for any java web start application

ensure you can launch application via the desktop shortcut

update the server JNLP file for the application.  e.g change the application title.

launch from the shortcut again.   it will never pick up the update to the JNLP file.  the shortcut won't be updated to reflect the new title.

if you launch directly from browser JNLP link, it works and will pick up the update.

this has been reported externally as well, see last comment here:

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6809125

regression from 6u13
also a seperate problem if <update check=background/>
When updating a jnlp file in the background updater we need to fix the shortcut(s)

Comments
EVALUATION two separate regressions from 6764455: 1.) When launching from a shortcut, the whole premiss of the original fix was that you do not need to check the network when running a webstart application from the web. The jnlp file javaws is given was already downloaded by the browser. But the fix didn't take this case into consi=deration, when launched from a shortcut, the jnlp file you are launched from is already in the cache. In this case we need to check the timestamp to see if it has been updated on the net. 2.) When doing background downloads. Before this series of performance fixes, there was no such thing as background downloading. We only checked in the background if an update was needed, then flagged the lap such that an update would occur on the next launch. With this fix there is background downloading of all resources (if update check=background) . The problem here was that if downloading the main jnlp file for an application or applet that had a shortcut set, there was no code to update the shortcut to point to the new jnlp file/ This can result in a shortcut that points to a no-longer existant file in the cache.
09-05-2009

EVALUATION also regression in LDUpdator - would download a main jnlp file w/o checking if shortcut needed to be updated.
08-05-2009

EVALUATION regression in updateFinalLaunchDesc caused by over optimazation
07-05-2009