JDK-5109847 : J2SE 142_06: Regression in java.beans.Introspector (property re-ordering)
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.beans
  • Affected Version: 1.4.2_06
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: solaris_9
  • CPU: generic
  • Submitted: 2004-10-01
  • Updated: 2004-11-18
  • Resolved: 2004-11-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.
Other
1.4.2_07 b02Fixed
Related Reports
Relates :  
Relates :  
Description
The regression is in java.beans.Introspector, when it gets the beanInfo for a class, the order of properties in the beanInfo is changed from 142_05 to 142_06.  The order in 142_05 is alphabetical.  I attached a test case to identify this.

What you need to do is to compile both Test.java and SOAPStruct.java and run java test.Test.

142_05:

65$ java test.Test

0: varFloat

1: varInt

2: varString



142_06:

64$ java test.Test

0: varInt

1: varString

2: varFloat 

Comments
EVALUATION I must first mention that the Introspector spec does not guarentee that properties will be returned in any particular order. However this is not the first instance of someone relying on the order anyway. The change in behavior happened after the fix for 4918902, which was backported to 1.4.2_06. This fix also caused problems for Tiger, prompting bug 5063390. The easiest resolution to this bug would be to backport the 5063390 fix to a 1.4.2 update release. Another option would be to move to Tiger. ###@###.### 2004-10-01
2004-10-01