JDK-6735003 : preload deployment common cache (plugin/webstart) with javafx libraries
- Type: Enhancement
- Component: deploy
- Sub-Component: deployment_toolkit
- Affected Version: 6u10,6u12
- Priority: P2
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic,x86
- Submitted: 2008-08-07
- Updated: 2010-09-17
- Resolved: 2008-09-12
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 b32Fixed  |
7Fixed |
Related Reports
|
Duplicate :
|
Description
JRE-Installer should pre-populate deployment cache with JavaFX Libraries. The JavaFX libraries should be setup as JNLP extensions in a well known permanent location (URL). The libraries should not be bundled with the JRE installer. At the end of the installation, we should launch "javaws -import [javafx url]" in background and have it bring down the libraries silently. We might need some changes to the deployment download engine and see what can we handle this background download efficiently, e.g, what to do if the client tries to start a javafx application while this backround download is still in progress.
Comments
|