[CXF-4818] The body and header appears in reverse order for outbound soap message

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.6.6
• Fix Version/s: 2.7.4, 2.6.7
• Component/s: Soap Binding
• Estimated Complexity: Unknown
• Assignee: Daniel Kulp
• Reporter: Haihong Xu
• Created: 08/Feb/13 15:59
• Updated: 09/Apr/13 15:15
• Resolved: 14/Feb/13 21:48

Description

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.