[
https://issues.apache.org/jira/browse/CXF-5244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13790625#comment-13790625
]
Sergey Beryozkin commented on CXF-5244:
---------------------------------------
I guess it is not strictly required because JAXRSInInterceptor is checking the
map and if it finds Content-Type or Accept then it also resets dedicated
message properties.
You probably moved because setting Content-Type in the handler was not having
any effect on selecting the resource classes, or may be methods,
try @PreMatching ContainerRequestFilter, it should work too and it will be
portable
> 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: 2.7.7, 3.0.0
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)
