RE: [OS-webwork] ActionTag changes

[Jason Carreira]

Title: Message

I've just changed this per what we talked about before... the ActionTag does now carry over the same ValueStack and pops off anything set during the call to the Action from the ActionTag, including the Action itself, before leaving the doEndTag().... -----Original Message----- From: Patrick Lightbody [mailto:[EMAIL PROTECTED] Sent: Monday, October 20, 2003 11:59 AM To: [EMAIL PROTECTED] Subject: RE: [OS-webwork] ActionTag changes John, I think jira is back up, can you log all these issues down. Thanks.   The action tag does not push anything on the stack. The difference between an action (with a velocity result) and an include of an action URL (with a velocity result) is that the include still requires a request dispatcher to be used. Since a second request is being made, there is an entirely new ActionContext, and thus ValueStack.   -Pat   -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Patterson Sent: Friday, October 17, 2003 5:23 AM To: Webwork Subject: [OS-webwork] ActionTag changes   I have just been having a look at the ActionTag using executeResult=true.  I wanted to put a couple of things in Jira but it seems to be down at the moment.   The tld specifies the id as required.  When using the tag to include content the id tag is not necessary.   The tld defines an attribute result but the property on the tag is executeResult.   It would be handy to have a 'value' attribute in addition to the 'name' attribute so that the action to execute can be specified at run time.   Is it correct that the main difference between using the Action tag and the Include tag for 'componentising' a page is that the Action tag uses the same value stack?    Does the Action tag push the action onto the stack?   John.