"One common use of Action chaining is to provide lookup lists (like for a dropdown list of states, etc). Since these Actions get put on the ValueStack, these properties will be available in the view."
see: http://wiki.opensymphony.com/space/Webwork+-+Why+would+I+use+Action+Chaining%3F
hope it helps!
Peter White wrote:
Hi gang,
I have an action that will either submit a form's contents, if it passes validation, or dispatch the form for completion if it doesn't pass validation. Basically, it's my way of being lazy so I don't have to write one action to render a form and post to another action to process it.
However, I've run into a hitch because the form will always fail validation until it is completed but I need to populate a drop-down field on it from a List attribute in the action which never gets populated because validation fails… So, what are my options here? Should I stick with two separate actions or use a component or interceptor to populate my list? Are there any other options that webwork provides that I haven't considered?
Thanks! Peter
------------------------------------------------------- This SF. Net email is sponsored by: GoToMyPC GoToMyPC is the fast, easy and secure way to access your computer from any Web browser or wireless device. Click here to Try it Free! https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
