The reason is that when the execute() is called in the doEndTag() you can be sure that all of the params have been set on the Action before it is executed... If execute() is called in doStartTag, none of the <ww:param> tags will be processed before it is executed.
Got it. Just do not know, not that there might not be, what situations an execute() for a directly requested *.jsp page is needed. Would an explicit <ww:execute> tag after the <ww:param>(s) be too cumbersome?
The reason this is implemented this way is that ActionContext's are created and set in only the one place... Therefore there can only be the previous ActionContext and the new ActionContext...
What about a Sitemesh decorator default.jsp and its child *.jsp(s)? Or nested tiles of *.jsp(s)? Could they have their own actions that upon return would need the old Action restored?
Fred.
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
