I searched for the
issue.
I finally figured
out that there are no issues direclty related to the problem of nested iterate
tags.
It is mentionned in
the isssue IBATIS-238, but only in the commentary of Jeff
Butler.
--
Quote
[ Permlink ]
We definitiely need something like this
for dynamic elements within an iterate tag. But I wonder if this is the right
way to solve it. Does this work for nested iterate tags? i.e. - can I do
[].[].someProperty?
I wonder if it might be better to specify something like var=xxx in the iterate tag (like the JSTL forEach syntax)?
Great start on a solution to this problem!
-- End quote
I wonder if it might be better to specify something like var=xxx in the iterate tag (like the JSTL forEach syntax)?
Great start on a solution to this problem!
-- End quote
This is where I saw
that the next evolution could handle a var attribute in iterate
tag.
Thanks to you
Brandon, I also remarked the link in your last message. I read the content
of the link, but I still wonder if everything would work as expected. This
is a very good start and it would need a real discution on how everything
should be modified. I approve the idea of keeping the simplicity of the
framework.
I would like to add
an idea myself to the proposition. In the <foreach> proposed tag, I think
it would be a good idea to access a property of the parameterClass in the same
way as struts nested tags allow (meaning using a #/somePropertyOfParameterClass#
or possibly something like #../someProperty# if we want a property of
the parent of the foreach item).
Please indicate me
where I should send these suggestions in the future.
Christian Poitras
Institut de recherches
cliniques de Montréal (IRCM)
[EMAIL PROTECTED]
