If on the other hand, the code is related to business logic that is really independent of the struts portion, then I would put this in a common class that can be reused from as many actions as need it. In a lot of my applications I use a facade for my actions to communicate with seperate objects relating to business logic.
This also has the nice benefit of keeping your business logic independent of the particular web solution (in this case Struts) you are using. In fact, you can keep your business logic the same if you decide to write a client server app instead!
sean
Why don't you just create an abstract action and extend it?
Danilo Gurovich
Manager, Web Development
LowerMyBills.com
[EMAIL PROTECTED]
2401 Colorado Ave., 2nd Floor Santa Monica, CA 90404
(310) 998-6412
-----Original Message-----
From: Ciaran Hanley [mailto:[EMAIL PROTECTED] Sent: Thursday, September 30, 2004 3:16 AM
To: Struts User Mailing List
Subject: Reusing methods across actions classes
Hey,
Bit of a dummy question here but I am wondering what is the best way to reuse methods across different action classes. Is it acceptable to make an instance of an action class within an action class so I can use one of its methods. Or would it be better to simply copy and paste the method into the both classes. Or should I extract all common methods into one class and create an instance of this class as required. Any suggestions?
CH
--------------------------------------------------------------------- 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]
