JDK-7052942 : Support FX runtime without bootclasspath
  • Type: Enhancement
  • Component: deploy
  • Sub-Component: deployment_toolkit
  • Affected Version: 7-client
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2011-06-09
  • Updated: 2011-09-22
  • Resolved: 2011-08-17
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.
JDK 7 JDK 8
7u2 b03Fixed 8Fixed
Description
Latest builds of FX2.0 do not rely on library path to load native libraries. 
Hence we can stop adding FX to the bootclasspath and can add it to the intemediate secure classloader. 
This will allow dynamic installation of JavaFX runtime in the existing JVM without relaunch.
This will also be improtant for future modularization efforts.
Comments
SUGGESTED FIX Add classloader to load JavaFX instead of using bootclasspath. Webrev at http://sa.sfbay.sun.com/projects/deployment_data/7-client/7052942/ Test: Manually test loading of JavaFX and regular applets.
01-08-2011
EVALUATION We can add a classloader to load JavaFX classes rather than bootclasspath, however, that's not enough to avoid relaunch. The problem with relaunch is that we have to avoid any instantiation of UI toolkit until we know FX or AWT should be used. Current implementation use AppContext and some other toolkit specific operation without clear state boundary, and some of those are performed before we know exactly what toolkit to use. We will need to clean up those situation to totally avoid relaunch.
01-08-2011