Return-Path: X-Original-To: apmail-cxf-issues-archive@www.apache.org Delivered-To: apmail-cxf-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 091BA10DD8 for ; Thu, 29 Aug 2013 16:46:57 +0000 (UTC) Received: (qmail 65509 invoked by uid 500); 29 Aug 2013 16:46:53 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 65437 invoked by uid 500); 29 Aug 2013 16:46:53 -0000 Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list issues@cxf.apache.org Received: (qmail 65393 invoked by uid 99); 29 Aug 2013 16:46:52 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Aug 2013 16:46:52 +0000 Date: Thu, 29 Aug 2013 16:46:52 +0000 (UTC) From: "Dmitry Treskunov (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CXF-5244) It is not possible to update Content-Type inside JAX-RS 2.0 ContainerRequestFilter MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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