[ http://issues.apache.org/jira/browse/BEEHIVE-988?page=all ] Jacob Danner closed BEEHIVE-988: --------------------------------
I've verified this manually and am working on a regression cases to submit later Closing. > control bean's generated BeanInfo doesn't use correct property names in the > presence of a @PropertySet.prefix attribute > ----------------------------------------------------------------------------------------------------------------------- > > Key: BEEHIVE-988 > URL: http://issues.apache.org/jira/browse/BEEHIVE-988 > Project: Beehive > Type: Bug > Components: Controls > Versions: V1, v1m1 > Reporter: Eddie O'Neil > Assignee: Eddie O'Neil > Priority: Critical > Fix For: 1.0.1 > > This is a bit of an ugly bug in the controls where the use of the > @PropertySet(prefix="foo") annotation doesn't result in generation of the > correct BeanInfo file for the control. For example: > @PropertySet(prefix="foo") > public @interface MyProperties { > public String aStringProperty(); > public int anIntProperty(); > } > the generated property accessors are: > getFooAStringProperty() > getFooAIntProperty() > but the BeanInfo only lists the property accessor methods as: > getAStringProperty() > getAIntProperty() > When attempting to load a generated ControlBean using the > java.beans.Introspector, the result is a stack trace about a missing property > accessor. This is fixed by specifying the correct JavaBean property accessor > methods in the BeanInfo file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
