|
Quick Lists
|
|
Bug ID:
|
6486655
|
|
Votes
|
0
|
|
Synopsis
|
REGRESSION: Standard MBean attributes and operations lose original interface order
|
|
Category
|
jmx:classes
|
|
Reported Against
|
|
|
Release Fixed
|
6u2(b01),
7(b03) (Bug ID:2143732)
|
|
State
|
10-Fix Delivered,
bug
|
|
Priority:
|
2-High
|
|
Related Bugs
|
|
|
Submit Date
|
26-OCT-2006
|
|
Description
|
My server side uses JDK6, my client side JDK5.
I call getMBeanInfo localy and remotely on the same standard MBean,
then check for equality calling MBeanInfo.equals
This call return false because the two MBeanInfo objects return the same values
in their MBeanFeatureInfo arrays but in a different order.
With JDK6, the alphabetic order seems to be used while in JDK5,
it's the declaration order that is used.
Posted Date : 2006-10-26 13:36:51.0
|
|
Work Around
|
N/A
|
|
Evaluation
|
It appears indeed that attributes and operations in a Standard MBean are now sorted, whereas in JDK 5.0 they appeared in the same order as the corresponding methods in the MBean interface. This does not violate the specification, but could surprise existing code. We should restore the JDK 5.0 behaviour.
Notice that the method eliminateCovariantMethods in this class has a comment about preserving order, which it does, but to no avail because the order is lost elsewhere.
Posted Date : 2006-10-26 15:11:32.0
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
|
