-
Bug
-
Resolution: Fixed
-
P4
-
None
-
b78
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8135828 | emb-9 | Alexandr Scherbatiy | P4 | Resolved | Fixed | team |
The javadoc for the java.awt.Toolkit getDefaultToolkit() method claims:
----------------------
If there is no "java.awt.headless" or it is set to false and there is a system property named "awt.toolkit", that property is treated as the name of a class that is a subclass of Toolkit; otherwise the default platform-specific implementation of Toolkit is used.
----------------------
It should be reconsidered is this property still useful after the modularization updated in JDK 9.
Se also Removing all methods that use the AWT peer types in JDK 9 email:
http://mail.openjdk.java.net/pipermail/awt-dev/2015-February/008924.html
----------------------
If there is no "java.awt.headless" or it is set to false and there is a system property named "awt.toolkit", that property is treated as the name of a class that is a subclass of Toolkit; otherwise the default platform-specific implementation of Toolkit is used.
----------------------
It should be reconsidered is this property still useful after the modularization updated in JDK 9.
Se also Removing all methods that use the AWT peer types in JDK 9 email:
http://mail.openjdk.java.net/pipermail/awt-dev/2015-February/008924.html
- backported by
-
JDK-8135828 Reconsider "awt.toolkit" property usage in java.awt.Toolkit getDefaultToolkit() method
-
- Resolved
-
- relates to
-
JDK-8037739 Remove API references to java.awt.peer and java.awt.dnd.peer packages in the JDK 9 timeframe
-
- Resolved
-