commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 12458] New: - BeanUtils.setProperty does not work with indexed properties
Date Mon, 09 Sep 2002 21:14:24 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12458>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12458

BeanUtils.setProperty does not work with indexed properties

           Summary: BeanUtils.setProperty does not work with indexed
                    properties
           Product: Commons
           Version: Nightly Builds
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: Bean Utilities
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: steven.davelaar@oracle.com


When using indexed struts html tags within a <logic:iterate> tag the generated 
fields are named like "id[34].propertyName". The number in brackets will be 
generated for every iteration and taken from ancestor.

The code in method setProperty first checks for nested expression. Nested 
expressions have a .dot in the property name. As shown above, indexed properties 
also have a dot in the name. This results in a NoSuchMethodException  thrown and 
catcahed by setProperty which ends execution. The code to poplualte a normal 
indexed property from the Http request is never executed.

This bug causes indexed properties to be never populated with the submitted 
values.

--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message