JDK-5047548 : Lazy downloading of parts with packages is broken
- Type: Bug
- Component: deploy
- Sub-Component: webstart
- Affected Version: 5.0,5.0u1
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- OS: generic,windows,windows_xp
- CPU: generic,x86
- Submitted: 2004-05-14
- Updated: 2012-10-09
- Resolved: 2004-09-01
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.
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 | JDK 6 |
|---|---|
| 5.0u1 01Fixed | 6Fixed  |
Description
The JNLP spec allows you to associate package names with parts (and thereby with jar resources). A Lazy jar can therefore list all the packages included in it in the jnlp file. (this is similar to Jar Indexing, which was later invented) This helps when a resource included in one of the listed packages is requested, the lazy jar known t.o contain that package is loaded first. But it dosn't work the other way around. If a resource is requested that isn't included in any of the jars with their packages listed, then all of the jars with their packages listed (and know not to contain the resource) are downloaded anyway. If a resource being sought is not in any of the packages listed, then none of the lazy jars associated with package listings should be downloaded.
Comments
|