JDK-7077787 : Preloader jars are checked for update even when update policy background and already in cache
  • Type: Bug
  • Component: deploy
  • Sub-Component: deployment_toolkit
  • Affected Version: 7-client
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2011-08-11
  • Updated: 2011-09-22
  • Resolved: 2011-08-17
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 7 JDK 8
7u2 b03Fixed 8Fixed
Description
* With tracing all on, run Fx sample applet with preloader multiple time:
http://jfx.sfbay.sun.com/hudson/job/presidio-deploy-scrum/label=windows-i586-14/253/artifact/artifacts/deployed/FadeInPreloader/
* Check console output to see first time there would be network trace: Downloaded <url> : <file>.
* Check console output in subsequent runs still see the same trace on the preloaders.jar.
Comments
EVALUATION Actually the fix is limited to have common facility in LaunchDownload.prepareCustomProgress() to be called with doUpdate param set to value true only if not all files are in cache, OR if update policy require update check. Fix checked in with changeset: 1024:f18bb99493cc ssh://###@###.###//javafx/client/7-client/deploy/deploy
15-08-2011
EVALUATION The download code path for preloader jar call GET to check if update is needed. The fix is to use HEAD instead.
11-08-2011