cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CXF-4141) response_code 500 ignored when set in JAXRSOutInterceptor.handleWriteException
Date Tue, 28 Feb 2012 13:03:48 GMT

     [ https://issues.apache.org/jira/browse/CXF-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sergey Beryozkin resolved CXF-4141.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.6
                   2.4.7
                   2.3.10
         Assignee: Sergey Beryozkin
    
> 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
>            Assignee: Sergey Beryozkin
>             Fix For: 2.3.10, 2.4.7, 2.5.3, 2.6
>
>
> 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

        

Mime
View raw message