[
https://issues.apache.org/jira/browse/CXF-5795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14056149#comment-14056149
]
Sergey Beryozkin commented on CXF-5795:
---------------------------------------
No, I'm not doubting that 202 responses may have entities, what I'm saying is
that CXF HttpConduit gets a null InputStream.
See
https://fisheye6.atlassian.com/browse/cxf/rt/transports/http/src/main/java/org/apache/cxf/transport/http/ChunkedUtil.java?r=876e532549f5ae1038947344f1a0431e5339bd4c,
getPartialResponse().
Can you confirm a 202 response actually does return an entity in your case ?
Please use a tcp trace to check what is actually returned and let me know
Cheers, Sergey
> Reading the entity from a Response with 202 - Accepted causes
> NullPointerException
> ----------------------------------------------------------------------------------
>
> Key: CXF-5795
> URL: https://issues.apache.org/jira/browse/CXF-5795
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
> Affects Versions: 2.7.11
> Environment: Apache CXF 2.7.11
> Reporter: Daniel Peder Dahlsveen
>
> The entity of a Response with HTTP status code 202 - Accepted is null. This
> causes a NullPointerException when calling response.readEntity().
> Furthermore, this bug seems to only occur when using the JAXRSClientFactory,
> and it was introduced in CXF 2.7.11.
> The stacktrace is of the NullPointerException:
> java.lang.NullPointerException
> at
> org.apache.cxf.jaxrs.impl.ResponseImpl.doReadEntity(ResponseImpl.java:345)
> at
> org.apache.cxf.jaxrs.impl.ResponseImpl.readEntity(ResponseImpl.java:286)
> at
> org.apache.cxf.jaxrs.impl.ResponseImpl.readEntity(ResponseImpl.java:276)
> To recreate the bug do the following:
> Create a REST service that returns a 202 - Accepted with a non-null entity.
> In our case, the service was for HTTP POST.
> Create a unit test that tests the service by creating a client with the
> JAXRSClientFactory and then reads the entity from the response.
> Both return Response.accepted(entity).build(); and return
> Response.status(Response.Status.ACCEPTED).entity(entity).build(); causes the
> bug.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
