|
Quick Lists
|
|
Bug ID:
|
4474875
|
|
Votes
|
0
|
|
Synopsis
|
Incremental updates fail if going from basic proto to version based.
|
|
Category
|
javawebstart:download_engine
|
|
Reported Against
|
1.0.1
|
|
Release Fixed
|
1.4.2(mantis)
|
|
State
|
10-Fix Delivered,
bug
|
|
Priority:
|
4-Low
|
|
Related Bugs
|
|
|
Submit Date
|
26-JUN-2001
|
|
Description
|
from mail:
Looking a littler closer at the download requests in your logfile for the
plus_dbu.jar file, I see the following:
Request 1: JnlpDownloadServlet(3): Request: /per-se/plus_dbu.jar
. This is a request for the file without using version protocol.
This gets downloaded correctly.
Request 2: JnlpDownloadServlet(3): Request:
/per-se/plus_dbu.jar?version-id=1.3.49
. This is a request for the file w/ the versioning protocol. This
also gets downloaded correctly.
Request 3: JnlpDownloadServlet(3): Request:
/per-se/plus_dbu.jar?version-id=1.3.56
. This request seems to be wrong from Javaws. It does NOT include
information
about the 1.3.49 version. Thus, a jardiff will never be returned. It
should have been:
/per-se/plus_dbu.jar?version-id=1.3.56¤t-version-id=1.3.49
It seems like Javaws gets confused because of first request, where you are
not using the version protocol.
|
|
Work Around
|
|
|
Evaluation
|
fix for 1.2
----------
I believe the problem is in DiskCache.getCacheEntries().
If the version arg is non-null, then the itr loop should do
itr.remove(); if ( versionId == null) not just if
(!(versionId == null) || vs.contains(versionId))
xxxxx@xxxxx 2002-07-24
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
 |