ExtendedBeanInfo Passes Empty Property Name to PropertyDescriptor Causing IntrospectionException: bad property name [SPR-8175]

[spring-projects-issues]

Rob Winch opened SPR-8175 and commented

When handling an ArrayList, the ExtendedBeanInfo Passes Emtpy Property Name to PropertyDescriptor Causing IntrospectionException: bad property name. This occurs in the latest development build of trunk and can be seen in the Greenhouse application. I have attached a patch that provides a junit and a fix.

---

Reference URL: http://forum.springsource.org/showthread.php?s=1c62fe0e73fde377348700ad8437a010&t=106697

Attachments:

• extendedbeaninfo-emptyproperty.patch (2.75 kB)
• mylyn-context.zip (1.18 kB)

Issue Links:

• Support injection against setter methods with non-void return types [SPR-8079] #12734 Support injection against setter methods with non-void return types
• Overhaul non-void JavaBean write method support [SPR-10029] #14663 Overhaul non-void JavaBean write method support
• Review ExtendedBeanInfo implementation [SPR-8347] #12995 Review ExtendedBeanInfo implementation

Referenced from: commits 0ee1256, 4a8be69, 158a392

2 votes, 1 watchers

[spring-projects-issues]

Chris Beams commented

Patch applied - thanks Rob!

[spring-projects-issues]

Chris Beams commented

A general note to watchers of ExtendedBeanInfo-related issues: #14663 is a major refactoring of ExtendedBeanInfo and overall support for non-void returning setter methods.

If you have submitted a reproduction project with this issue, we have run it through its paces against these new changes, but we would like to ask you to do the same against your actual applications.

Please consider updating your dev or test builds to work against 3.1.4.BUILD-SNAPSHOT and/or 3.2.0.BUILD-SNAPSHOT to verify, and we would appreciate any feedback, even if it's to let us know that all is well. So that we can consolidate feedback, please add your comments to #14663, and mention the original issue(s) that you were watching.

Thanks!

Note also that testing against 3.1.4 is preferable to 3.2.0 because ExtendedBeanInfo is always in the code path in the latter, while in 3.2.0 we've optimized things such that ExtendedBeanInfo is only in play for bean classes that have one or more non-void returning setter methods.