FX Swing interop, which comprises JFXPanel and SwingNode, requires tight coupling between the Swing classes in the java.desktop module and the FX classes in the javafx.swing module.
The following internal packages are exported from java.desktop to javafx.swing:
exports java.awt.dnd.peer to javafx.swing;
exports sun.awt to javafx.swing;
exports sun.awt.dnd to javafx.swing;
exports sun.awt.image to javafx.swing;
exports sun.java2d to javafx.swing;
exports sun.swing to javafx.swing;
As part of an overall effort to reduce or eliminate the use of internal packages from core module by javafx.* modules, we need to limit the use of internal interfaces to those that really are needed, and then formalize these interfaces so we have a more robust solution.
The following internal packages are exported from java.desktop to javafx.swing:
exports java.awt.dnd.peer to javafx.swing;
exports sun.awt to javafx.swing;
exports sun.awt.dnd to javafx.swing;
exports sun.awt.image to javafx.swing;
exports sun.java2d to javafx.swing;
exports sun.swing to javafx.swing;
As part of an overall effort to reduce or eliminate the use of internal packages from core module by javafx.* modules, we need to limit the use of internal interfaces to those that really are needed, and then formalize these interfaces so we have a more robust solution.
- blocks
-
JDK-8202451 Swing interop fails when run with a security manager with standalone SDK
- Closed
-
JDK-8195798 ☂ Address dependencies in javafx.* modules on internal APIs of core modules
- Resolved
- is blocked by
-
JDK-8202199 Provide public, unsupported JDK API for JavaFX/Swing interop
- Resolved
- relates to
-
JDK-8210092 Remove old javafx.swing implementation
- Resolved
-
JDK-8210615 Swing interop requires qualified exports when run with JDK 10
- Closed