Return-Path: X-Original-To: apmail-cxf-users-archive@www.apache.org Delivered-To: apmail-cxf-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 415A69DA8 for ; Tue, 1 May 2012 17:57:05 +0000 (UTC) Received: (qmail 22108 invoked by uid 500); 1 May 2012 17:57:04 -0000 Delivered-To: apmail-cxf-users-archive@cxf.apache.org Received: (qmail 22063 invoked by uid 500); 1 May 2012 17:57:04 -0000 Mailing-List: contact users-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@cxf.apache.org Delivered-To: mailing list users@cxf.apache.org Received: (qmail 22051 invoked by uid 99); 1 May 2012 17:57:04 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 May 2012 17:57:04 +0000 X-ASF-Spam-Status: No, hits=2.9 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [64.95.72.241] (HELO mxout.myoutlookonline.com) (64.95.72.241) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 May 2012 17:56:56 +0000 Received: from mxout.myoutlookonline.com (localhost [127.0.0.1]) by mxout.myoutlookonline.com (Postfix) with ESMTP id D852B8428EB for ; Tue, 1 May 2012 13:56:33 -0400 (EDT) X-Virus-Scanned: by SpamTitan at mail.lan Received: from S10HUB002.SH10.lan (unknown [10.110.2.1]) by mxout.myoutlookonline.com (Postfix) with ESMTP id A7AAE841EDC for ; Tue, 1 May 2012 13:56:13 -0400 (EDT) Received: from S10BE002.SH10.lan ([::1]) by S10HUB002.SH10.lan ([::1]) with mapi id 14.01.0355.002; Tue, 1 May 2012 13:56:13 -0400 From: Andrei Shakirin To: "users@cxf.apache.org" Subject: Copiing Request SOAP Headers to Fault response Thread-Topic: Copiing Request SOAP Headers to Fault response Thread-Index: Ac0nwDiVY2/86Gn+Q5WQWNdKT9VPDg== Date: Tue, 1 May 2012 17:56:12 +0000 Message-ID: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [188.104.84.234] Content-Type: multipart/alternative; boundary="_000_D225CD69196F3F4A9F4174B2FCA06F885D7102S10BE002SH10lan_" MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_D225CD69196F3F4A9F4174B2FCA06F885D7102S10BE002SH10lan_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, Actually JAXWSMethodInvoker and AbstractJAXWSMethodInvoker contain code to = copy request soap headers (except security one) to SOAP Fault: AbstractJAXW= SMethodInvoker.updateHeader(). I see some use cases when it is not really desired: 1) Request SOAP headers contains some labelling information about requ= est elements and they make sense only with request 2) Request SOAP headers extending request elements with meta-informati= on If request headers are copied into fault response, they can be invalid in r= esponse context and cause undesired effects: 1) it makes response processing on the client side more difficult, esp= ecially if processing interceptor is called before incoming fault message i= s recognized and placed into exchange.getInFaultMessage() 2) response fault message has larger size Proposal is to define context property that give user the possibility to sw= itch-off coping request headers into fault response. If proposal makes sense, I will prepare Jira with patch. Regards, Andrei. --_000_D225CD69196F3F4A9F4174B2FCA06F885D7102S10BE002SH10lan_--