-
Bug
-
Resolution: Fixed
-
P2
-
6
-
rc
-
b01
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2143732 | 7 | Eamonn McManus | P3 | Closed | Fixed | b03 |
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.
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.
- backported by
-
JDK-2143732 REGRESSION: Standard MBean attributes and operations lose original interface order
-
- Closed
-