Not sure if the last time I sent this out it got lost in folks threaded
email filtering because it appeared to be a sub-post under my Zero
config thread. I figured I'd resent it out before I start working on
this and open an enhancement for it.
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 including XWork and the
ConfigurationManager.
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 feature to this refactoring 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 any plugins that are
participating in the configuration and initialization process.
-bp
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
