cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Bannii <>
Subject CXF & NIO & JAX-RS 2
Date Mon, 14 Jul 2014 16:01:54 GMT

This February there was a thread titled "Server Side Asynchronous processing support via CXF
& NIO support" regarding an NPE thrown at when trying to use
AsyncResponse. I get a simmilar stacktrace, and I prepared an own simple test maven project
demonstrating the issue (attached to the email).

In short:
 1. I use latest Jetty: 8.1.15.v20140411.
 2. In web.xml i have both 'version="3.0"' and '<async-supported>true</async-supported>'.
 3. My rest resource api is declared using AsyncResponse.

And still i get this:

    at org.apache.cxf.jaxrs.impl.AsyncResponseImpl.initContinuation(
    at org.apache.cxf.jaxrs.impl.AsyncResponseImpl.<init>(
    at org.apache.cxf.jaxrs.utils.JAXRSUtils.processParameter(
    at org.apache.cxf.jaxrs.utils.JAXRSUtils.processParameters(
    at org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.processRequest(
    at org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.handleMessage(
    at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(

Am I missing something? Can it be some async setup that is missing in my jaxrs:server declaration
inside applicationContext.xml? Currently i have there:

    <jaxrs:server address="/api">
            <ref bean="apiResourceBean"/>
            <ref bean="jacksonProvider"/>

Best regards

View raw message