JDK-6764455 : Avoid network requests if everything is cached and JNLP has
  • Type: Enhancement
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: 6
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2008-10-28
  • Updated: 2010-09-26
  • Resolved: 2009-05-13
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 JDK 7
6u14 b03Fixed 7Fixed
Related Reports
Relates :  
JDK-6838214 - launch from desktop shortcuts of java web start application will not pick up JNLP update from server
Description
In the ideal situation webstart startup logic should behave as follows:

If all of the following is true:
  a) initial JNLP file is local (even if it is in browser cache yet)
  b) all required JNLP files contain <update check="background">
  c) all required resources are present in the cache

Then startup of webstart application should not require any network requests.

Background thread should check for updates and install updates to the cache.
Comments
EVALUATION Reuse background update logic introduced for plugin2. Attempt to start from cache only. If this fails then try again with network connections enabled. In case if application fails with error mark it as one requiring foreground update check (to check if update will resolve the failure).
25-02-2009