-
Bug
-
Resolution: Fixed
-
P3
-
8u20
Thread.currentThread().setContextClassLoader(a);
Application.launch(args);
Thread.currentThread().getContextClassLoader() != not a
This is only a minor inconvenience for my apps (which use the UpdateFX updates framework) because you can always just run
Thread.currentThread().setContextClassLoader(ExampleApp.class.getClassLoader());
as the first line in start(Stage) ... but it'd be nice if it wasn't necessary. I poked through the code but it seems starting the JFX app thread is done possibly inside native code.
Application.launch(args);
Thread.currentThread().getContextClassLoader() != not a
This is only a minor inconvenience for my apps (which use the UpdateFX updates framework) because you can always just run
Thread.currentThread().setContextClassLoader(ExampleApp.class.getClassLoader());
as the first line in start(Stage) ... but it'd be nice if it wasn't necessary. I poked through the code but it seems starting the JFX app thread is done possibly inside native code.
- is blocked by
-
-
- Resolved
-
- relates to
-
JDK-8102035 Change launcher to always call the main method for standalone JavaFX applications
-
- Resolved
-
-
-
- Resolved
-