> I'm working on refactoring JXTG so that it will be easier to support and
> develop. I'm aware about that you have access the request object etc
Great ! Don't know if i can help (time), but if you have a road map or
something like that, i would be happy to contribute.
> differently depending on if you are using flow or not and also that the
> eval tag is less well designed. What more weird behaviours are you
> thinking of?
Variable nature and scope (kind of non-mutable that you can overwrite ?),
but someone could tell me this a feature :-). Perhaps i've miss something,
but look what i need to do to retrieve a value incremented inside a forEach
loop:
<jx:set var="globalvars" value="${java.util.HashMap(5)}"/>
<jx:set var="dummy" value="${globalvars.put('a_count', 0)}"/>
...
<jx:set var="a_count" value="${globalvars.a_count}"/>
<jx:forEach begin="1" end="3" varStatus="i">
...
<jx:if test="#{$node/@path != ''}">
...
<jx:set var="a_count" value="${a_count+1}"/>
<jx:set var="dummy" value="${globalvars.put('a_count', a_count)}"/>
</jx:if>
</jx:forEach>
<jx:out>this is my count: ${globalvars.a_count}</jx:out>
It would be easiest (and efficient) to do
<jx:set var="a_count" value="0"/>
<jx:forEach begin="1" end="3" varStatus="i">
...
<jx:if test="#{$node/@path != ''}">
...
<jx:set var="a_count" value="${a_count+1}"/>
</jx:forEach>
<jx:out>this is my count: ${a_count}</jx:out>
the fact that "set" make always a "new define" is quite annoying at first
glance (functional programming ?).
Regards.
