United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
JDK-7077787 : Preloader jars are checked for update even when update policy background and already in cache

Details
Type:
Bug
Submit Date:
2011-08-11
Status:
Resolved
Updated Date:
2011-09-22
Project Name:
JDK
Resolved Date:
2011-08-17
Component:
deploy
OS:
generic
Sub-Component:
deployment_toolkit
CPU:
generic
Priority:
P3
Resolution:
Fixed
Affected Versions:
7-client
Fixed Versions:
7u2 (b03)

Related Reports
Backport:

Sub Tasks

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
                                     
2011-08-15
EVALUATION

The download code path for preloader jar call GET to check if update is needed.
The fix is to use HEAD instead.
                                     
2011-08-11



Hardware and Software, Engineered to Work Together