JDK-8097323 : [packager] javafxpackager loads AWT unconditionally
  • Type: Bug
  • Component: deploy
  • Sub-Component: packager
  • Affected Version: 8
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2013-10-18
  • Updated: 2015-06-12
  • Resolved: 2013-10-24
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 8
8Fixed
Related Reports
Blocks :  
Duplicate :  
Duplicate :  
Description
The NoJavaFXCallback class is used to check the JRE version. However it is an ancestor of the awt Component, so it loads AWT. When FX starts is thinks that it is running embedded which leads to a number of bugs.
Comments
Verified in b124
23-01-2014

SQE: To verify this: 1) Take any simple FX program (once that doesn't use Swing interop) 2) Use javafxpackager to generate a jar file 3) Run that file with "java -verbose:class ..." and verify that no AWT classes are loaded.
17-01-2014

http://hg.openjdk.java.net/openjfx/8/graphics/rt/rev/b5b14c01d4d6
24-10-2013

This will be checked into today and make it into b113
21-10-2013

I think there might already be another issue filed relating to this (I'll look it up). I can work with Mark one this. We should no longer need NoJavaFXFallback in FX 8.
18-10-2013

The problem is in the com.javafx.main.Main:62 - then we are checking if it's an old JRE using the NoJavaFXFallback class.
18-10-2013

This issue is a critical one for Scene Builder 2.0 dev preview.
18-10-2013