If you really like having the perform method separate from the execute, just keep it. But extend the Action class to create a new base class. That way, if perform is ever permanantly removed, your code will still work. For instance, I created a base class that extended Action and called it CounselorAction ( for all the actions applicable to the business rules for counselors - whoever they are) and then packed a lot of common code before/after the call to the perform method inside the execute method. This way, all the action classes for "counselors" inherit all the common functionality. I ignore the deprecated warning in this case since I know what it is. An alternative that I have seen is to create a second command pattern with is own base class and child classes for the business logic and execute those from the execute method in the child Action class but then the number classes that you have to write is doubled for each action. -Tony julian green <[EMAIL PROTECTED]> wrote: Andrew Hill wrote:
>Your upgrading from 1.02 > Yes, and until the next non beta release is made that is where I will be staying. Just wanted to know what I am in for when I upgrade. > >In 1.1 you use the execute() method. > Thankyou. Julian > > >-----Original Message----- >From: julian green [mailto:[EMAIL PROTECTED]] >Sent: Wednesday, 22 January 2003 20:23 >To: Struts Users Mailing List >Subject: perform method deprecated?? > > >Ive downloaded struts 1.1b3 and im being told that all the perform >methods I developed are deprecated. What is the new method? > >Ive got alot of code to refactor. > >Julian > > >-- >To unsubscribe, e-mail: > >For additional commands, e-mail: > > > >-- >To unsubscribe, e-mail: >For additional commands, e-mail: > -- To unsubscribe, e-mail: For additional commands, e-mail: --------------------------------- Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now
