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 9036] New: - "setValue" method broken ?
Date Mon, 13 May 2002 14:34:19 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=9036>.
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=9036

"setValue" method broken ?

           Summary: "setValue" method broken ?
           Product: Commons
           Version: 1.0 Beta 1
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: JXPath
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: jpochat@sopragroup.com


Hi

Using filtering attributes with "setValue" method doesn't seem to work. For 
example :

context.getPointer("/employeeList[firstName='Dmitri']/firstName").setValue
("NewDmitri");

The new value is cached into the pointer object, but the property writer method 
is not invoked, so the bean is not modified. It works well with non filtered 
path.

Method "ValueUtils.setValue(Object bean, PropertyDescriptor propertyDescriptor, 
Object value)" shoudn't be called instead of "ValueUtils.setValue(Object 
collection, int index, Object value)" ?

Thanks.

--
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