-
Bug
-
Resolution: Fixed
-
P4
-
1.2.0
-
tiger
-
generic
-
generic
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2109806 | 5.0 | Eamonn McManus | P4 | Resolved | Fixed | team |
The Javadoc and PDF are inconsistent concerning these values. Javadoc says 1 to 5, PDF says 0 to 6. Implementation follows Javadoc, so suggest PDF should be changed to be consistent.
Change to the above suggestion: changing implementation and Javadoc so they allow 0 to 6 should not affect existing code, while changing everything to allow only 1 to 5 will break code that previously worked on independent implementations that followed the PDF spec. IBM has such an implementation, and WebSphere is such code, so changing to 0-6 is the right solution.
###@###.### 2003-05-30
Change to the above suggestion: changing implementation and Javadoc so they allow 0 to 6 should not affect existing code, while changing everything to allow only 1 to 5 will break code that previously worked on independent implementations that followed the PDF spec. IBM has such an implementation, and WebSphere is such code, so changing to 0-6 is the right solution.
###@###.### 2003-05-30
- backported by
-
JDK-2109806 Allowed values for ModelMBeanNotificationInfo's severity inconsistent
-
- Resolved
-
- relates to
-
JDK-4884972 Errata for the JMX 1.2 spec in Tiger
-
- Closed
-