Ok. I did some thinking about this on the plane and here's what I'm thinking:
<webwork:action name="foo" id="foo"> <webwork:param name="bar">123</webwork:param> <webwork:param name="baz">456</webwork:param> </webwork:action> The action is executed in the closing tag after the params have been set and the action is bound into the page context (like a jsp:usebean). This was really the only way I could think of to have a good lifecycle and be parameterized. Then, later, you can do: <webwork:push value="@foo"> <webwork:property value="bar"/> <webwork:property value="myGeneratedProperty"/> </webwork:push> Which gets the Action from the PageContext and pushes it onto the ValueStack. You could also just access properties using the "@foo.bar"... At least, I think that's how the Ognl notation accesses objects in the PageContext :-) Thoughts? Jason > -----Original Message----- > From: Pat Lightbody [mailto:[EMAIL PROTECTED] > Sent: Saturday, March 22, 2003 3:23 PM > To: [EMAIL PROTECTED] > Subject: Re: [OS-webwork] Action Tag > > > Nah, you've got it all wrong. It's really quite a nice way to > integrate data in to your UI tags, for example: > > <ww:action name="InfoTypeLoader"> > <ui:select label="'Select an InfoType'" name="'infoType'" > list="possibleInfoTypes"/> </ww:action> > > InfoTypeLoader has a getPossibleInfoTypes() method that > returns a List, for example. Without the ww:action tag, you'd > have to make all your various actions do this > getPossibleInfoTypes() method, which sucks. > > -Pat > > PS: I'm off to Europe for 2 weeks in like 15 minutes, talk to > you guys later! > > > ----- Original Message ----- > From: "Jason Carreira" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Saturday, March 22, 2003 11:21 AM > Subject: RE: [OS-webwork] Action Tag > > > > Ok, having read this thread, I'm trying to figure out what the > > intended use of the Action tag is. I've personally never > used it, so > > perhaps a discussion of the need / usage of it would make the right > > thing to do more clear. I understand that the non-deterministic > > execution of Actions is a real problem, so a good lifecycle model > > should be one requirement. What are the others? > > > > I'd rather take a little time and try to do this right than > put in a > > quick fix. The execute tag just seems a little hacky to me, > and it's > > one more tag, which has non-trivial requirements of the JSP > developer > > (i.e. bind an Action to an id above). It also seems too much like > > regular JSP, which I detest, IMHO. > > > > Jason > > > > > -----Original Message----- > > > From: Heng Sin Low [mailto:[EMAIL PROTECTED] > > > Sent: Friday, March 21, 2003 11:57 PM > > > To: OS-Webwork > > > Subject: [OS-webwork] Action Tag > > > > > > > > > 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 > > > > > > > > > ------------------------------------------------------- > > 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 > > > > ------------------------------------------------------- > 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 > ------------------------------------------------------- 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
