JDK-4403113 : Incremental update functionality is not working.
  • Type: Bug
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: 1.0
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_nt
  • CPU: x86
  • Submitted: 2001-01-09
  • Updated: 2001-05-07
  • Resolved: 2001-05-07
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.
Other
1.0.1 1.0.1Fixed
Description
javaws 1.0 will not append the "current-version-id=X.X" field to an http
request when requesting one version of a resource when another version is in
the cache.  This prevents a servlet from sending jardiff files to use 
incremental updates.  Instead, the whole request jar is downloaded.

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: 1.0.1 FIXED IN: 1.0.1 INTEGRATED IN: 1.0.1 VERIFIED IN: 1.0.1
2004-08-31

EVALUATION This is caused by DiskCache.getCachedEntries() pruning out all the non-matching entries. Fixed by adding one more arg, boolean exact, to getCachedEntries, if set true it will act as before, if false, will leave one (if lesser version exists) non-matching entry in the list if no entries match. andy.herrick@East 2001-01-09
2001-01-09