Auch Arron,
Are you sure all those "instanceof" checks are a good idea? Adding
another nested tag would require you to adapt the NestedPropertyHelper,
which isn't clean design IMHO.
And I wouldn't have noticed this if I wasn't checking an NestedIterate
bug. nested:iterate behaves differently than logic:iterate, which really
shouldn't be. I narrowed it down to this:
<logic:iterate name="orderitems" id="service" property="serviceForms"
indexId="servIdx">
generates
<snip>
java.lang.Object service = null;
service = (java.lang.Object) pageContext.findAttribute("service");
java.lang.Integer servIdx = null;
servIdx = (java.lang.Integer) pageContext.findAttribute("servIdx");
</snip>
while
<nested:iterate name="orderitems" id="service" property="serviceForms"
indexId="servIdx">
simply doesn't.
The only place I can see something happens between
IterateTag.doStartTag() and NestedIterateTag.doStartTag() is precisely
in NestedPropertyHelper. So I guess all those instanceofs already
created a bug ...
I'm searching further to find the bug itself, but if you would beat me
at it, I would appreciate it :)
Cheers,
tomK
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
