struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Husted" <hus...@apache.org>
Subject Re: Struts plugin and configuration/initialization
Date Tue, 01 May 2007 18:44:19 GMT
It would be nice if the refactoring would make it easier to implement
"Automatic Alias ActionConfigs"

* https://issues.apache.org/struts/browse/WW-1522

As I remember, we ran aground of the same kind of problem.

On 4/30/07, Brian Pontarelli <brian@pontarelli.com> wrote:
> Right now the struts plugin architecture is setup to allow plugins to be
> processed once XWork has been setup, configured and initialized. This
> makes it difficult to change the configuration and initialization
> process for Struts and Xwork without sub-classing the FilterDispatcher
> and overriding methods in a Dispatcher sub-class. Although this isn't
> difficult, it doesn't make using a plugin as simple as dropping it into
> the WEB-INF/lib directory, nor does it allow multiple plugins to change
> the configuration/initialization process.
>
> I'd like to propose fixing this by moving the plugin handling a level
> higher and allowing plugins to add beans that could participate in the
> configuration and initialization of everything.
>
> I haven't got a firm interface or class structure in mind, but I wanted
> to start some discussion first before I went down to that level of detail.
>
> Perhaps another plugin feature would be to move the dependency injection
> that is leveraged by XWork (effectively Guice pre 1.0) higher so that it
> could be leveraged by this new plugin structure as well.
>
> -bp

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Mime
View raw message