[
https://issues.apache.org/jira/browse/CXF-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13217439#comment-13217439
]
Benjamin Shults commented on CXF-4141:
--------------------------------------
No, I'll do that now.
> response_code 500 ignored when set in
> JAXRSOutInterceptor.handleWriteException
> -------------------------------------------------------------------------------
>
> Key: CXF-4141
> URL: https://issues.apache.org/jira/browse/CXF-4141
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
> Affects Versions: 2.5.2
> Environment: tomcat 7.0.26, Java 1.6,
> Reporter: Benjamin Shults
> Fix For: 2.5.3
>
>
> I have a scenario where the call to writer.writeTo in
> JAXRSOutInterceptor.serializeMessage throws an exception.
> Before throwing the exception, the writer writes to the outputStream.
> When write.writeTo throws the exception, handleWriteException calls
> message.put(Message.RESPONSE_CODE, 500).
> However, my HTTP client is seeing the response come back with HTTP response
> code 200.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
