United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
JDK-7052942 : Support FX runtime without bootclasspath

Details
Type:
Enhancement
Submit Date:
2011-06-09
Status:
Resolved
Updated Date:
2011-09-22
Project Name:
JDK
Resolved Date:
2011-08-17
Component:
deploy
OS:
generic
Sub-Component:
deployment_toolkit
CPU:
generic
Priority:
P2
Resolution:
Fixed
Affected Versions:
7-client
Fixed Versions:
7u2 (b03)

Related Reports
Backport:

Sub Tasks

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.
                                     
2011-08-01
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.
                                     
2011-08-01



Hardware and Software, Engineered to Work Together