Take a look at the value stack via the debug tag.
Usually the property tag will keep stepping through the value stack
until a getter for the property is found (the object for the current
iteration is placed on the top of the value stack). Although, if you
are explicitly defining the object (via id and #test) there shouldn't be
a problem.
/Ian
tom tom wrote:
Hi,
I got three iterations which I tried as below in the
jsp, First two and Array of certain DTO and last
iterator is a String array. There is no jsp
compilation error, but the issue is it produced
misleading results.
Is there any limitation in S2 for the depth of the
iteration. Is this way of using recommended?
Sometimes where it is suppose to print empty value it
prints something else (looks like from the previous
iterator)
<s:iterator value="#session.ITER1" id="qnn">
....
....
<s:iterator value="#qnn.ITER2" id="qa">
....
....
<s:iterator value="#qa.ITER3" id="test">
<s:property value="#test" />
</s:iterator>
</s:iterator>
</s:iterator>
____________________________________________________________________________________
Park yourself in front of a world of choices in alternative vehicles. Visit the
Yahoo! Auto Green Center.
http://autos.yahoo.com/green_center/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
