You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Sergey Beryozkin (JIRA)" <ji...@apache.org> on 2013/08/30 14:37:52 UTC
[jira] [Comment Edited] (CXF-5244) It is not possible to update
Content-Type inside JAX-RS 2.0 ContainerRequestFilter
[ https://issues.apache.org/jira/browse/CXF-5244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13754648#comment-13754648 ]
Sergey Beryozkin edited comment on CXF-5244 at 8/30/13 12:37 PM:
-----------------------------------------------------------------
Also fixed an issue with customizing accept types in pre-matching filters
was (Author: sergey_beryozkin):
Also fixed an issues with customizing accept types in pre-matching filters
> 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
> Assignee: Sergey Beryozkin
> Fix For: 3.0.0, 2.7.7
>
>
> 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