JDK-6682407 : missing update check for second level extension JNLP file
- Type: Bug
- Component: deploy
- Sub-Component: webstart
- Affected Version: 6u10
- Priority: P3
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2008-03-31
- Updated: 2010-09-17
- Resolved: 2008-06-27
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 | JDK 7 |
|---|---|
6u10 b22Fixed  |
7Fixed |
Description
One bug I noticed in LauchDownload.isUpdateAvailable() is that it goes only one level down to extensions from the main app jnlp. If an extension has updated extensions, they won't be checked. All jars (included in all extensions) are checked though. e.g a.jnlp -> b.jnlp (component ext) -> c.jnlp (component ext) there is no update check for c.jnlp
Comments
|