Most JavaFX classes are not serializable. However, we have a few that are, including:
* JFXPanel (since it inherits from javax.swing.JCompoent)
* Event (since it inherits from java.util.EventObject)
At the very least, the JFXPanel class should have the same disclaimer as its superclass. Namely:
"The current serialization support is appropriate for short term storage or RMI between applications running the same version of Swing."
For Event we either need to suppress the warning or document the private fields.
We might split this into two bugs depending on how we address serialization of events.
* JFXPanel (since it inherits from javax.swing.JCompoent)
* Event (since it inherits from java.util.EventObject)
At the very least, the JFXPanel class should have the same disclaimer as its superclass. Namely:
"The current serialization support is appropriate for short term storage or RMI between applications running the same version of Swing."
For Event we either need to suppress the warning or document the private fields.
We might split this into two bugs depending on how we address serialization of events.
- blocks
-
JDK-8325075 Enable -Werror for javadoc to fail on any warnings
-
- Resolved
-
-
JDK-8271083 ☂ Missing documentation in JavaFX API
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
-
- Resolved
-
(1 links to)