On Fri, 13 Aug 2004 12:51:44 -0700, Jim Barrows <[EMAIL PROTECTED]> wrote: > > > > -----Original Message----- > > From: Rick Reumann [mailto:[EMAIL PROTECTED] > > Sent: Friday, August 13, 2004 1:06 PM > > To: Struts Users Mailing List > > Subject: Re: Loosing request attributes > > The problem you are describing comes up a lot on this list - when > > validation fails and you are back on the initial form you > > will not have > > access to the previous set request attributes. It is for this reason > > that I now rarely ever set my mapping validate to "true" and instead > > call validate() from my Action after the form submits. The reason for > > this is when validation fails (ActionErrors/Messages return) > > I can then > > call a private setUp() method in my Action that is used to set up my > > form with any other request attributes that should always be there. > > I'm curious why using the input parameter doesn't work for you? >
Indeed ... the feature is working as it was designed, based on application user expectations that, if errors occur, whatever they typed in is redisplayed (even if it is wrong) so that it can be corrected. That's the way that any rich GUI client works, and nobody wants to use apps that force you to fill an entire form in again simply because you made one mistake. Craig --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
