Note that the main motivation for the extensions package
at the link below was to avoid having to always extend
the ActionServlet.
As far as altering the behavior of things
like the action classes, forwards, etc.. I think a good
event/listener model could be used for most of those cases.
I think that the event/listener registration could
neatly be tied into the extensions package. You would
create your org.strutsx.extensions.Extension subclass,
and register for all of the events you are interested in
there.
--Ron
Ted Husted writes:
> Rob,
>
> If you have a chance take at look at this
>
> < http://www.rpsenterprises.com/struts/index.html >
>
> and let us know what you think.
>
> I agree that is very important that we look for ways for people to add
> new functionality without subclassing everything in sight.
>
> "Leland, Rob" wrote:
> >
> > It would be nice if struts could be extended
> > without having to place new code under
> > the org.apache.struts.action classes,
> > but just by dropping a separate jar file
> > under some directory that would self-register.
> >
> > So what is the best way to extend struts
> > so that it stays lean ?
> >
>
> < ... />
