Hmmmm.... I suppose that setting place to go back to in the validate() method would work, except that I have defined a single actionForm class that i utilize in all pages, another "benefit" of dispatch actions and this would require me to determine what action i was validating before making a decision in the validate method of the form, and that doesn't seem to be very good design to me.
-----Original Message----- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Monday, June 23, 2003 7:52 AM To: 'Struts Users Mailing List' Subject: RE: DispatchAction and input Joel wrote: > I guess that's the root of my problem. > The place that it should go to when validation fails is > different for each method. I would always want it to go > back to the page that was submitted to produce the error I've never tried this, but... 'ActionMapping mapping' is part of the signature of the validate method. Would it be possible to override validate() and call mapping.setInput("whatever.jsp") before calling super.validate()? Worth a try, I guess. Although "go back where you came from" is a common Struts problem. I just put a value in the request or session, but that may not appeal to everyone. -- Wendy Smoak Applications Systems Analyst, Sr. Public Affairs, Information Resources Management Arizona State University, Tempe AZ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
