[
https://issues.apache.org/jira/browse/CXF-5795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053901#comment-14053901
]
Jeffrey Samarziya commented on CXF-5795:
----------------------------------------
I'm sorry, I don't understand the assumptions here. You seem to be saying that
a 202 response should not contain an entity, but I find that contradicts the
HTTP 1.1 specification.
Section 10.2.3 states in part,
bq. The entity returned with this response SHOULD include an indication of the
request's current status...
which implies that a 202 response may in fact contain an entity.
Reference: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.2.3
> 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)
