United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
JDK-4837340 : Cache versioning fails to work in 1.4.1 and higher releases

Details
Type:
Bug
Submit Date:
2003-03-25
Status:
Closed
Updated Date:
2003-12-02
Project Name:
JDK
Resolved Date:
2003-08-07
Component:
deploy
OS:
generic,windows_2000
Sub-Component:
plugin
CPU:
x86,generic
Priority:
P3
Resolution:
Fixed
Affected Versions:
1.4.1
Fixed Versions:
1.4.1_07 (07)

Related Reports
Backport:
Backport:
Duplicate:

Sub Tasks

Description
Even when cache version are specified for jar files, plug-in connects to the server to get the time stamp and last modified date

                                    

Comments
CONVERTED DATA

BugTraq+ Release Management Values

COMMIT TO FIX:
1.4.1_07
1.4.2_02
generic
tiger

FIXED IN:
1.4.1_07
1.4.2_02
tiger

INTEGRATED IN:
1.4.1_07
1.4.2_02
tiger

VERIFIED IN:
1.4.1_07
1.4.2_02


                                     
2004-06-14
EVALUATION

Too late for mantis, committing to tiger
###@###.### 2003-03-25

The initialized CachedJarLoader is not used if the version check is passed. Because of this, the caching code results in timestamp check even if the required version is on the user system.
###@###.### 2003-07-14
                                     
2003-07-14



Hardware and Software, Engineered to Work Together