Frank
From: "Joe Hertz" <[EMAIL PROTECTED]> Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]> To: "'Struts Users Mailing List'" <[EMAIL PROTECTED]> Subject: RE: Pulling Punches Date: Mon, 21 Jun 2004 20:49:18 -0400
> This is not a great solution, for all the reasons that action > chaining is considered dangerous. After the validation fails, Struts > would begin an entire re-execution of the RequestProcessor chain, and > the archives have plenty of discussion on why that's unpredictable > and worth avoiding.
Joe-
Not to change the subject *too* much, but what is the recommended way of handling following case:
User clicks a button causing Action A to fire. Brings him to a page with data it needs (say for a dropdown box).
User submits form on this page, causing Action B to fire with validation. Validation fails, bringing him back to page with dropdown box. Since Action A did NOT fire, dropdown box isn't populated.
Short of sticking that data into a session, what is the way one should handle this?
An "action chain" like I described is what Andrew Hill suggested to me on this list, and nobody screamed :-)
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar – get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]