When I am using design #3 my action mappings always specify that validate="false". Those methods that do require validation explicitly call the validate method of the bean. Those methods that do not require validation don't call the method. So no conditioning is needed in the form bean for design #3 :)
Matt ----- Original Message ----- From: "Shane Mingins" <[EMAIL PROTECTED]> To: "'Struts Users Mailing List'" <[EMAIL PROTECTED]> Sent: Thursday, September 25, 2003 4:42 PM Subject: RE: [Poll] action mappings > > -----Original Message----- > > From: Sgarlata Matt [mailto:[EMAIL PROTECTED] > > Sent: Friday, 26 September 2003 2:14 a.m. > > To: Struts Users Mailing List > > Subject: Re: [Poll] action mappings > > > > OK, I think I understand #1 now. However, I still disagree with it ;) If > > you are using the same form bean and display components, you can define a > > single action mapping and thus eliminate duplicate configuration > > information > > in the struts-config file. > > > In my case I am using style #1 because some actions require the form bean to > be validated and some do not. I did not like the idea of conditioning the > validation in the form bean validate() method. > > Anyone have thoughts or comments on that? > > Shane > > --------------------------------------------------------------------- > 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]
