cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sergey Beryozkin <sberyoz...@gmail.com>
Subject Re: Discuss: CXFServlet and spring ApplicationContext
Date Tue, 30 Nov 2010 15:35:49 GMT
Hi Christian

On Tue, Nov 30, 2010 at 12:16 AM, Christian Schneider <
chris@die-schneider.net> wrote:

> One thing I found is the spring DispatcherServlet:
>
> http://static.springsource.org/spring/docs/2.5.x/api/org/springframework/web/servlet/DispatcherServlet.html
>
> Could we simply use this servlet to route requests to our services and have
> no own servlet at all?


CXFServlet lets us customize the way requests are dealt with. Example, it
can be configured to route the requests to other destinations.

cheers, Sergey



> Spring uses this for their own remoting protocols.
>
> Best regards
>
> Christian
>
>
> Am 30.11.2010 01:10, schrieb Christian Schneider:
>
>  I am currently trying to dig deeper into the http transport.
>>
>> One part of the code that I really don´t like is the CXFServlet. If I
>> understand correctly it is being used when you want to have a servlet
>> transport together with a spring application context.
>> In the documentation (http://cxf.apache.org/docs/servlet-transport.html)
>> there are two ways to use it:
>>
>> You can either use ContextLoaderListener from spring or let it pull up a
>> new context.
>>
>> I don´t know if it is only because of the second option but there is some
>> really ugly code in there to find or pull up an application context and work
>> directly with it.
>> So my point is that we should let spring do this. Can´t we just let spring
>> inject whatever we need?
>>
>> Best regards
>>
>> Christian
>>
>>
> --
> ----
> http://www.liquid-reality.de
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message