cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitry Treskunov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CXF-5244) It is not possible to update Content-Type inside JAX-RS 2.0 ContainerRequestFilter
Date Thu, 29 Aug 2013 16:46:52 GMT

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

Dmitry Treskunov updated CXF-5244:
----------------------------------

    Description: 
As I understand, it wasn't possible to update headers inside JAX-RS 2.0 ContainerRequestFilter.

Is was fixed in this issue https://issues.apache.org/jira/browse/CXF-4986.

But now update of Content-Type header inside of @PreMatching filter doesn't affect further
processing - 
suitable MessageBodyReader is selected using initial Content-Type but not new one.  
    
> It is not possible to update Content-Type inside JAX-RS 2.0 ContainerRequestFilter 
> -----------------------------------------------------------------------------------
>
>                 Key: CXF-5244
>                 URL: https://issues.apache.org/jira/browse/CXF-5244
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-RS
>    Affects Versions: 2.7.6
>            Reporter: Dmitry Treskunov
>
> As I understand, it wasn't possible to update headers inside JAX-RS 2.0 ContainerRequestFilter.

> Is was fixed in this issue https://issues.apache.org/jira/browse/CXF-4986.
> But now update of Content-Type header inside of @PreMatching filter doesn't affect further
processing - 
> suitable MessageBodyReader is selected using initial Content-Type but not new one.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message