JDK-4690736 : Add Jar indexing to Java Web Start, and update JNLPClassLoader.
- Type: Enhancement
- Component: deploy
- Sub-Component: webstart
- Affected Version: 6
- Priority: P2
- Status: Resolved
- Resolution: Fixed
- OS: generic,windows_2000,windows_xp
- CPU: generic,x86
- Submitted: 2002-05-23
- Updated: 2005-02-16
- Resolved: 2005-02-16
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.
| JDK 6 |
|---|
6 b24Fixed  |
Related Reports
|
Duplicate :
|
|
|
Duplicate :
|
Description
Name: ch7115 Date: 05/23/2002 Java Web Start does not support Jar Indexing which is a part of the Jar File Spec. In stead it has "eager" and "lazy" mode of download of the jar files. The problem is that we have to mention all the jar file names, some of our apps has 120 jar files, in the jnlp file with download=lazy set. It would be of great help to stick to the standard on-demand load of the jar files through Jar Indexing. Even when you specify download=lazy, it is unclear how the Java Web Start finds out the class,jar file mapping. (Review ID: 146929) ======================================================================
Comments
|