-
Bug
-
Resolution: Fixed
-
P3
-
5.0, 6
-
b63
-
generic, sparc
-
generic, solaris_2.6
-
Verified
Version 1.0 of the JMX API did not explicitly specify the serial form of all classes, and this form was essentially incorrect for certain classes. Version 1.1 of the API rectified this by defining the serial form explicitly for all classes. At this time code was introduced to allow continued serial interoperation with the 1.0 classes if a system property is specified. The serialVersionUID of the relevant classes is different when the property is present than when it is absent. Since the serialVersionUID is not a compile-time constant, it does not appear in the Javadoc output for these classes. The classes should be augmented with appropriate @serial tags so that the correct serialVersionUID appears in the documentation. Otherwise compatible implementations need to analyse the Reference Implementation (e.g. with the serialver tool) in order to determine the correct value.
###@###.### 2005-04-12 12:33:27 GMT
###@###.### 2005-04-12 12:33:27 GMT
- duplicates
-
JDK-4884443 Javadoc doesn't specify serialVersionUID for several JMX classes
-
- Closed
-
- relates to
-
JDK-6267224 Migration, interoperation failures for serialized javax.xml.namespace.QName inst. betw EE 1.4,SE 5.0
-
- Resolved
-
-
JDK-6362514 ClassAttributeValueExp and NumericValueExp are missing a serialVersionUID
-
- Closed
-
-
JDK-8334165 Remove serialVersionUID compatibility logic from JMX
-
- Resolved
-
-
JDK-6338881 Javadoc should provide a way to include a non-constant serialVersionUID in the Serialized Form page
-
- Closed
-