Return-Path: 
 <issues-return-24371-apmail-cxf-issues-archive=cxf.apache.org@cxf.apache.org>
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 4A204D66B
	for <apmail-cxf-issues-archive@www.apache.org>;
 Thu, 14 Feb 2013 21:49:13 +0000 (UTC)
Received: (qmail 15995 invoked by uid 500); 14 Feb 2013 21:49:13 -0000
Delivered-To: apmail-cxf-issues-archive@cxf.apache.org
Received: (qmail 15970 invoked by uid 500); 14 Feb 2013 21:49:13 -0000
Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@cxf.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@cxf.apache.org>
List-Post: <mailto:issues@cxf.apache.org>
List-Id: <issues.cxf.apache.org>
Reply-To: dev@cxf.apache.org
Delivered-To: mailing list issues@cxf.apache.org
Received: (qmail 15957 invoked by uid 99); 14 Feb 2013 21:49:13 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Feb 2013 21:49:13 +0000
Date: Thu, 14 Feb 2013 21:49:13 +0000 (UTC)
From: "Daniel Kulp (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.12631467.1360339157635.290511.1360878553058@arcas>
In-Reply-To: <JIRA.12631467.1360339157635@arcas>
References: <JIRA.12631467.1360339157635@arcas>
Subject: [jira] [Resolved] (CXF-4818) The body and header appears in reverse
 order for outbound soap message
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-4818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Kulp resolved CXF-4818.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.6.7
                   2.7.4
    
> The body and header appears in reverse order for outbound soap message
> ----------------------------------------------------------------------
>
>                 Key: CXF-4818
>                 URL: https://issues.apache.org/jira/browse/CXF-4818
>             Project: CXF
>          Issue Type: Bug
>          Components: Soap Binding
>    Affects Versions: 2.6.6
>            Reporter: Ivan
>            Assignee: Daniel Kulp
>             Fix For: 2.7.4, 2.6.7
>
>
> In the scenario below, the body and header elements are in reverse order, which will cause issue for client application.
> Step to reproduce :
> a. Use WebServiceProvider as the server side, and return a soap message with the content below:
> <SOAP-ENV:Envelope xmlns:SOAP-ENV=\"http://schemas.xmlsoap.org/soap/envelope/\"><SOAP-ENV:Body><provider>my message</provider></SOAP-ENV:Body></SOAP-ENV:Envelope>
> b. Enabling addressing for the server/client side
> The interceptor chain will be something like :
> Chain org.apache.cxf.phase.PhaseInterceptorChain@29de29de. Current flow:
>   setup [PolicyOutInterceptor]
>   pre-logical [MAPAggregatorImpl, SwAOutInterceptor, SoapHeaderOutFilterInterceptor, SecurityVerificationOutInterceptor]
>   post-logical [SoapPreProtocolOutInterceptor]
>   prepare-send [MessageSenderInterceptor, MessageModeOutInterceptor]
>   pre-stream [LoggingOutInterceptor, AttachmentOutInterceptor, StaxOutInterceptor]
>   pre-protocol [SAAJOutInterceptor, MAPCodec, PolicyBasedWSS4JOutInterceptor, UsernameTokenInterceptor]
>   write [SoapOutInterceptor]
>   marshal [BareOutInterceptor]
>   post-protocol [PolicyBasedWSS4JOutInterceptorInternal]
> It seems that, although we add a header checing in the SAAIOutInterceptor, while those addressing headers are not there at that time, then SoapOutInterceptor will add the header after the existing body elements.

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