Agreed with dave, But maybe another point, You said you already have a class all actions extend, right?
Is it said somewhere that the actions can extend one class only? I mean, if it's needed by the architecture, you can create a whole action hierarchy... And if you'd need multiple inheritance - use delegates :-) As to you another option, I know different people on this list like to instantiate actions directly, but as for me, it's forbidden in my team, because it brings a lot of problems with ressource sharing if you count to instantiate an action once, and do it multiple times. So in my opinion: First choice action hierarchy Second choice helper classes Or maybe a good combination of both :-) Regards Leon > -----Ursprüngliche Nachricht----- > Von: Dave Newton [mailto:[EMAIL PROTECTED] > Gesendet: Montag, 18. Juli 2005 23:18 > An: Struts Users Mailing List > Betreff: Re: Manually Instantiating Action classes > > a k wrote: > > >What is a better way in this scenario? In particular, is it bad to > >manually instantiate Action classes? > > > > > I don't know if it's "bad" per se, but if it's shared > functionality then from an architectural standpoint I would > think it'd better to move it into a helper class. > > Dave > > > > --------------------------------------------------------------------- > 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]
