[
https://issues.apache.org/jira/browse/CXF-5795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14095514#comment-14095514
]
Mathieu Durand commented on CXF-5795:
-------------------------------------
Hi guys,
I started from a tutorial project I found and was able to reproduce the problem
in a simple test case.
The tutorial project was originally setup with CXF 2.7.6 and I was not able to
reproduce the problem with this version. However, after updating to 3.0.1, I
was able to reproduce it. I also went back to 3.0.0 and I have the same
NullPointer described by Philippe. [Demo project attached cxf-demo.zip].
Start the demo project with mvn tomcat:run and execute the Tester1 test.
> 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
> Assignee: Sergey Beryozkin
> Fix For: 2.7.12, 3.0.1
>
> Attachments: cxf-demo.zip
>
>
> 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)
