Hi Sergey,
I first thought the CXFServlet would be enough as it does not require a
spring context.
Of course it still requires the spring dependencies. So I recreated a
CXFNonSpringServlet that works like
the CXFServlet without the Spring context and that has no dependencies
to spring. I also made the CXFServlet extend the CXFNonSpringServlet as
they can
share most of the code. I also made the CXFJaxrsNonSpringServlet extend
the CXFNonSpringServlet so it also has no dependencies on spring.
So I hope it should all work again as expected.
The windows trunk has three test failures. Do you think they are caused
by my changes?
Christian
Am 29.03.2011 13:35, schrieb Sergey Beryozkin:
Hey Christian
I was about to restore the CXFNonSpringServlet hierarchy but it actually was
removed (alongside with temporarily introduced CXFSpringServlet).
We really need to restore CXFNonSpringServlet - users do depend on it.
Please accept not all CXF users are Spring users :-). And I can't have
CXFNonSpringJAXRSServlet requiring spring dependencies which is not what its
name promises :-)
I'll restore CXFNonSpringServlet as you are busy with the important HTTP
refactoring work. I'll just add it as a new resource because reverting your
original merge and all the other ones are probably very tricky now
Sergey
On Mon, Mar 28, 2011 at 9:06 PM, Sergey Beryozkin<[email protected]>wrote:
--
----
http://www.liquid-reality.de
