Problem with the SOAP adapter !

Question

Hi!
We are trying to use a WebServices from XI.
In the WSDL file that we have imported and use'd in
our mapping the information about the soap header look's
like this :
<wsdlsoap:header message="impl:serviceRequest" part="toCountry" use="literal" />
<wsdlsoap:header message="impl:serviceRequest" part="fromCountry" use="literal" />
<wsdlsoap:header message="impl:serviceRequest" part="language" use="literal" />
<wsdlsoap:header message="impl:serviceRequest" part="customerCodeOwner" use="literal" />
<wsdlsoap:header message="impl:serviceRequest" part="customerCode" use="literal" />
<wsdlsoap:header message="impl:serviceRequest" part="userId" use="literal" />
<wsdlsoap:header message="impl:serviceRequest" part="userPassword" use="literal" />
But then the message leave the SOAP adapter
it looks like this:
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
<SOAP:Header/>
<SOAP:Body>
<ns1:serviceRequest xmlns:ns1='http://www.dnbnordic.com/brg/NRGDecisionSupportDSC/wsdl'>
<nRGDecisionSupportDSCRequest>
<ns2:criteria xmlns:ns2='http://www.dnbnordic.com/brg/NRGDecisionSupportDSC/request'>
<ns2:socialSecurityNumberApplicant>XXXXXXXXXX</ns2:socialSecurityNumberApplicant>
<ns2:conversationCode>X</ns2:conversationCode>
</ns2:criteria>
</nRGDecisionSupportDSCRequest>
<toCountry>XX</toCountry>
<fromCountry>XX</fromCountry>
<language>XX</language>
<customerCodeOwner>SYD9001</customerCodeOwner>
<customerCode>XXXXXXX</customerCode>
<userId>XXXX</userId>
<userPassword>XXXXXX</userPassword>
</ns1:serviceRequest>
</SOAP:Body>
</SOAP:Envelope>
The SOAP header info. is in the body !
Ofcourse the message fails !!
Any ideas ??
//Stig

Answer 1

Hi Stig,
Although specified in the WSDL 1.1 spec, the use of soap:header is quite rare.
And having a soap header consisting of multiple parts and not referring to single XSDL element is a bit in conflict with the document/literal approach.
Bottom line: please try and convince your business partner to not use the soap:header trick and stick to standard document/literal web services.
Kind regards, Guy Cretgs