DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39040>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39040

           Summary: Refactor Struts initialization to ServletContextListener
           Product: Struts
           Version: Nightly Build
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Action
        AssignedTo: [email protected]
        ReportedBy: [EMAIL PROTECTED]


Opening an enhancement ticket in order to generate some discussion and possibly
give a volunteer an idea for a project :-)

As part of migrating to Action 2, I thought that it might be a good idea to try
to have Struts configured by a ServletContextListener instead of concentrating
that initialization in the servlet.  The main idea would be that this would
steer any compatibility solution towards dispatching requests using a single
mechanism (presumably a future version of WebWork's FilterDispatcher) which
could set up a better framework for sharing and blending than simply leaving a
Struts 1.x ActionServlet in your config until you've factored out all of your
actions.

There would be a lot of tasks to this, but it seems that the first would be
simply factoring the initialization code out of ActionServlet in the Struts 1.x
line so that its basic functionality can be verified in the field.  

Comments?  Volunteers?

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to