On 26/11/12 03:23, Willem jiang wrote:
When you use camel-cxfrs, or camel-cxf component, it is using CXF continuation 
by default.
You can go through the code to check out how we use it :)

I wonder how how can a cxfrs consumer be enhanced to support JAX-RS 2.0 suspended invocations (which are initialized when a given resource method has a javax.ws.rs.container.AsyncResponse parameter) ?

With this style it is possible to get the same continuation reused/suspended many times, as opposed to a 'managed' continuation style currently supported by Camel where effectively only a single suspend for a given continuation thread is done, and which is resumed after a method returns ? At the moment it seems that by the time the AsyncResponse application code is finally ready to respond the Camel thread which was able to return a response to the client has gone to the end of the route...

Sorry if I got it wrong...


Sergey




Reply via email to