cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Klapste (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-5244) It is not possible to update Content-Type inside JAX-RS 2.0 ContainerRequestFilter
Date Wed, 09 Oct 2013 17:00:45 GMT

    [ https://issues.apache.org/jira/browse/CXF-5244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13790614#comment-13790614
] 

Jason Klapste commented on CXF-5244:
------------------------------------

Sounds correct-- and I'm fine with your suggestion-- ie updating the PROTOCOL_HEADERS (and
it isn't actually much more work at all). I am *not* updating CONTENT_TYPE and ACCEPT_CONTENT_TYPE--
looks like that isn't needed. Can you confirm?

As a side note, this interceptor was originally a Request Filter but we moved it to an interceptor--
can't remember why but we had a good reason ;)

> 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)

Mime
View raw message