JDK-8101853 : Enhance JavaFX launcher to allow Java launcher to directly launch JavaFX application jars
  • Type: Enhancement
  • Component: javafx
  • Sub-Component: application-lifecycle
  • Affected Version: 8
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2012-12-06
  • Updated: 2015-06-16
  • Resolved: 2012-12-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 8
8Fixed
Related Reports
Blocks :  
Description
In order to allow the Java launcher to properly start a JavaFX application while supporting all of the expected features of JavaFX applications, the JavaFX launcher code must be enhanced to allow the Java launcher to (at a minimum) pass a jar file path.

Comments
External JDK bug link: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=8004547
21-12-2012

Pushed to graphics scrum, changeset cbfa786ea560
17-12-2012

Note that this is only a *basic* implementation to allow for the changes on the SE side. A follow-up issue has been filed to track implementing the full launcher feature set.
17-12-2012

Proposed changes: http://cr.openjdk.java.net/~ddehaven/javafx/RT-26751/webrev.1/
17-12-2012

This is depended upon by the following JDK issue: https://jbs.oracle.com/bugs/browse/JDK-8004547
07-12-2012

I propose adding a new method to com.sun.javafx.application.LauncherImpl something like the following: public static void launchApplication(final String jarPath, final String mainClass, final String[] args) With the following expected behavior: - if jarPath is specified then the Jar is loaded, processed and launched by LauncherImpl directly - else if mainClass is specified then that class is loaded (if not already) and started, similar to the existing launchApplication methods - In the case where both are provided, whether mainClass is honored or not is up for discussion but the intent of the Java launcher is that only one argument will be provided, the other will be null
06-12-2012