The ticket is WW-1369 [1] and its goal is to make it possible do deploy
two Struts 2 filter dispatchers with completely different configurations
side-by-side in the same web application. As I dig down into this, it
is becoming quite apparent this would be a huge change, and before I do
anything, I want to run it by everyone.
To make this work, most uses of the static keyword in both XWork and
Struts 2 would have to be removed. In their place, there would be an
Application object, which would have getters and setters to manage the
previously statically managed instances. Application would be able to
find itself via a threadlocal, initialized by either the filter or
portlet dispatcher in Struts. This "context object" is different than
ActionContext, because Application contains instances that are shared
among all requests for a given filter/portlet instance, where
ActionContext handles request-level instances.
The objects to be moved over include DispatcherUtils, (Struts)
Configuration, LocalizedTextUtils, various XWork factories for objects
like ActionProxy and ActionInvocation, and ObjectFactory.
Perhaps the end goal wouldn't be worth the effort, I don't know. I
think it would be a nice design feature, but I wanted to get more
feedback from others before I dive into this change that would
fundamentally alter both XWork and Struts 2.
Don
[1] http://issues.apache.org/struts/browse/WW-1369
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
