> Not that I am aware. The paramsPrepareParamsStack to my knowledge > handles validation at the very end; so by the time validation has > happened; the model has already been prepared by the prepare() method.
Right, I see you said that earlier, sorry. So, why do you want to show what they entered, especially if it is so wrong? It seems satisfactory to represent the previously correct response. Still, if you need this, you could probably make use of ParameterAware and store that information somewhere where it can be accessed by your error display mechanism? I haven't used it before though, so just a thought. It might be applicable? I'm curious. If you are using ModelDriven, then why do you load your model in prepare()? Why not in getModel? I don't think behavior will be any different though since that interceptor is on the same side of the stack as prepare. - Eric From: "CRANFORD, CHRIS" <chris.cranf...@setech.com> To: "Struts Users Mailing List" <user@struts.apache.org> Date: 05/19/2011 01:16 PM Subject: RE: Struts2 Validation w/ModelDriven Not that I am aware. The paramsPrepareParamsStack to my knowledge handles validation at the very end; so by the time validation has happened; the model has already been prepared by the prepare() method. -----Original Message----- From: Eric Lentz [mailto:eric.le...@sherwin.com] Sent: Thursday, May 19, 2011 11:58 AM To: Struts Users Mailing List Subject: Re: Struts2 Validation w/ModelDriven > So when this error condition is met and the user redirected back to the INPUT form; the > field where they had entered "xyz" is now the original default > initialized value. Can't you check the action error and not refresh the model when there is an error? --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
