> -----Original Message----- > From: Nicolas De Loof [mailto:[EMAIL PROTECTED] > Sent: Friday, November 21, 2003 2:58 PM > To: Struts Users Mailing List > Subject: Re: best practice to avoid chaining actions > > > > > > Hello, > > > > If action chaining is a design error, then the struts-example that > > comes with struts distributions has a design error, saveSubscription > > forwards to editRegistration.do! > > > > Anyway, what I do is keep validation off action classes, by moving > > them off to action forms using validator and/or overridden > validate() > > methods. (Business logic validations that need access to > the data model must > > be in the model ofcourse, and not in action classes.) > > You're right, my description was a little short about this : > > In Action1, we use business model validation methods to > validate some form datas : to know if user is allowed to use > some datas he entered for the business process he want's to begin. > If the logic itself is in the model and action1 only makes the call to validate the user's inputs, I would guess it is ok to put it in the same action that fetches and populates data for page2. > > > > > Cheers, > > Krishna > > > > > --------------------------------------------------------------------- > 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]
