Bill, Isn't setting the input to another action sort of a bad idea? Wouldn't that cause the framework to start all over internally - request processing everything from scratch and all that? Wouldn't forwarding to a tile with a tiles controller work better (i.e. less processing power) in that situation?
Regards, David -----Original Message----- From: news [mailto:[EMAIL PROTECTED] Behalf Of Bill Siggelkow Sent: Wednesday, November 24, 2004 9:37 AM To: [EMAIL PROTECTED] Subject: Re: Post Validation You're on the right path, Lee. Instead of setting the "input" to the JSP, set it to an action, which creates your pick lists and stuffs them in the request, that precedes the JSP. -Bill Siggelkow Lee Harrington wrote: > I'm using DynaValidator forms. Works great, except when you have pick > lists and a validation fails. When the validation fails, it calls the > form, but the code that puts the pick lists in the request scope isn't > rerun. > > No biggie....I put my lists in the session scope. > > However, I don't want them hanging around forever. Wondering if there > is a "post Validate" section somewhere that I could put code in to > destroy the session variables. > > Better yet, a "preForm" section that is run even when Validate fails > so I could populate the lists in that scenario. > > Lee --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
