JDK-6362514 : ClassAttributeValueExp and NumericValueExp are missing a serialVersionUID
  • Type: Bug
  • Component: core-svc
  • Sub-Component: javax.management
  • Affected Version: 6
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2005-12-13
  • Updated: 2010-07-29
  • Resolved: 2006-02-18
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6
6 b73Fixed
Related Reports
Relates :  
JDK-6253903 - Serialized Form javadoc for JMX API should list serialVersionUID of all serializable classes
Relates :  
JDK-6338881 - Javadoc should provide a way to include a non-constant serialVersionUID in the Serialized Form page
Relates :  
JDK-6344759 - JMX spec should mandate more clearly the 12 javax.management.*Exp private classes
Description
We are facing a side effect of the combination of the fixes for 6344759 and 6253903.
As of Mustang b63, classes ClassAttributeValueExp and NumericValueExp are missing a serialVersionUID according the Serial Form pages.

These two classes do have serialVersionUID defined but because of a problem with non-constant serialVersionUID values it doesn't show up in the Serial Form pages, and because these classes aren't public the serialVersionUID that we recently added (was the fix of the defect #6344759) to the class doc comment doesn't show up either.
Comments
EVALUATION ClassAttributeValueExp and NumericValueExp are 2 classes which, among a few other JMX classes, define their serialVersionUID as a *blank* final constant which is initialised to the appropriate value in a static initializer block (see 6253903). As long as the RFE 6338881 is not implemented, the javadoc tool does not allow to cleanly put the serialVersionUID information in the serialized forms javadoc pages. As the ClassAttributeValueExp and NumericValueExp are not public classes, putting their serialVersionUID in the classes main javadoc is useless. Therefore, the remaining possibility to have this information show up is to add the serialVersionUID values in the documentation of the existing serializable fields of these classes.
02-02-2006