Taking your advice, it means that I would have two different action mappings, one for the init step and the second for the actual action (send). But then I will have to write something like <html:link page="/InitForgotPassword.do?action=init"> which is a bit strange to write again the "init", and it is needed cause the ForgotPasswordAction.java needs this 'action' parameter to distinguish between the two. Hmm..
Erez -----Original Message----- From: Adam Hardy [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 06, 2003 11:43 AM To: Struts Users Mailing List Subject: Re: Actions Best Practice Erez Efrati wrote: > One of the problem I found with 'action=init' method, is that the > validation is activated automatically for both cases (both init & send), > and fails of course on the 'init' cause no field is yet in the form. So > I was forced to configure 'validate=false' and call it manually in the > Action code. > Option B would be compacter. You can write two action mappings in struts-config to distinguish the calls, where one has no validation and the other does. I know some people don't like having extra action mappings in their struts-config, but I believe that is what they are there for. Adam --------------------------------------------------------------------- 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]
