I notice the action tag and lazyvalue stuff have landed in cvs and it follows
the 1.3 pattern which I think could be confusing at times. For e.g, it is not
deterministic when the action will actually be executed and you have to be
carefull when using the param tag with it. Exception from the actual execution
of action are being hidden as well.
For instance
<webwork:action name="abc.action">
<webwork:param name="startRow" value="result.current"/>
jsp content
</webwork:action>
will not work and this could be confusing for newbie. Also, if the action is
not being reference in the jsp content, executing it at the </webwork:action>
stage is rather pointless.
May be we should just add a nested execute tag to make this simpler and we can
get rid of all the lazyvalue stuff from action proxy too ( I feel it is an
awkward and unnecessary solution ).
for e.g, the example above can be rewritten as
<webwork:action name="abc.action">
<webwork:param name="startRow" value="result.current"/>
<webwork:execute>
jsp content
</webwork:execute>
</webwork:action>
OR
<webwork:action name="abc.action" id="myaction">
<webwork:param name="startRow" value="result.current"/>
</webwork:action>
<webwork:execute name="myaction">
jsp content
</webwork:execute>
Regards,
Low
__________________________________________________
Do you Yahoo!?
Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
http://platinum.yahoo.com
-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
