[ http://issues.apache.org/jira/browse/IBATIS-131?page=all ]
Brandon Goodin updated IBATIS-131: ---------------------------------- Fix Version: 2.2.0 (was: 2.1.5) Description: When using an iterate-tag to loop a list, one cannot point to the current element in attributes of inner tags, for example, the following fails: <iterate property="myList"> <isEqual property="myList[].someProperty" compareValue="true"> $myList[].anotherProperty$ </isEqual> </iterate> iBATIS tries to index the property myList with an empty string, but it should use the current element (the []-notation works fine within inner tags), when an index is supplied it works just fine... was: When using an iterate-tag to loop a list, one cannot point to the current element in attributes of inner tags, for example, the following fails: <iterate property="myList"> <isEqual property="myList[].someProperty" compareValue="true"> $myList[].anotherProperty$ </isEqual> </iterate> iBATIS tries to index the property myList with an empty string, but it should use the current element (the []-notation works fine within inner tags), when an index is supplied it works just fine... > Fix use of list[]-notation in propertyattributes of dynamic tags > ---------------------------------------------------------------- > > Key: IBATIS-131 > URL: http://issues.apache.org/jira/browse/IBATIS-131 > Project: iBatis for Java > Type: Bug > Components: SQL Maps > Environment: All are affected. > Reporter: Niels Beekman > Assignee: Brandon Goodin > Fix For: 2.2.0 > > When using an iterate-tag to loop a list, one cannot point to the current > element in attributes of inner tags, for example, the following fails: > <iterate property="myList"> > <isEqual property="myList[].someProperty" compareValue="true"> > $myList[].anotherProperty$ > </isEqual> > </iterate> > iBATIS tries to index the property myList with an empty string, but it should > use the current element (the []-notation works fine within inner tags), when > an index is supplied it works just fine... -- 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