Sounds like you need one more request parameter to distinguish between the a new request and a request coming after finishing an action.
Token processing might be a good option which prevents the user from book marking. Do a saveToken() in the AnnuityAction. If the previous and next are form "submit"'s rather than "links" then the "token" is automatically put as a hidden parameter if you use "<html:form/>" tag; otherwise you have to take the burden of tacking on that token as a request parameter. In the validate method; check for the validity of the token. (isTokenValid() is available in the org.apache.struts.action.Action). Since you are checking it from the form; you don't have that utility method available. Nevertheless, it's simple to check. Just compare the value of the token that's coming in the request to that of the value in the session; if they match; don't do the validation On Thu, 13 Jan 2005 13:58:23 -0500, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Sorry, I seem to have spoken too soon. The method paramater will have a value > because the previous button has been pressed. I don't want to say we won't > validate on previous or next, since we need to, I just need to not validate if > struts is coming from another action > > > --------------------------------------------------------------------- > 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]
