Hi Glen,
I think the spring context loader listener is enough for us to get the
application context.
And Using the name of CXFNonSpringServlet is just want to let user know
the servlet can work without Spring.
Willem.
Glen Mazza wrote:
Am Mittwoch, den 31.10.2007, 05:40 +0000 schrieb [EMAIL PROTECTED]:
Author: ningjiang
Date: Tue Oct 30 22:40:03 2007
New Revision: 590565
URL: http://svn.apache.org/viewvc?rev=590565&view=rev
Log:
CXF-1072 Added CXFNonSpringServlet for using ServletTransport without Spring
Hmmm...how about calling it CXFGenericServlet instead of
CXFNonSpringServlet? WDYT?
Also, in the future (I haven't analyzed this much so I may be very wrong
here), I wonder if we should have CXFServlet extend Spring's
HTTPServletBean[1]? That is a base class of SpringMVC's web framework
DispatcherServlet[2] that apparently allows for web.xml configuration,
and also specifying the location of the cxf.xml file within the web.xml.
Regards,
Glen
[1] http://tinyurl.com/3dplml
[2] http://tinyurl.com/3du74g
