Web Service operation not in SOAP request

Question

Hi There,
I have a problem with the SOAP receiver adapter.
I have created an external definition and uploaded a wsdl file. Several messages have been created out of the file.
In my mapping I fill the message structure from the wsdl file. When I send the message to the Web Service I get an error back.
The reason for this error seam to be a missing tag under the SOAP:Body element. Because when I create a SOAP request with the XMLSPY, it looks like this:
<SOAP:Body>
  <m:setVendor xmlns:m="http://..." ...>
    <ns8:v xmlns:ns8="http://...">
But in the message from the XI adapter the <m:setVendor..> tag is missing:
<SOAP:Body>
  <ns8:v xmlns:ns8="http://...">
This m: tag seems to be the operation of the web service.
Has anybody an Idea how to solve this?
Is the error in the SOAP adapter or in the message definition?
By the way, can I display the complete SOAP message that has been sent out from the adapter with any XI tool (including SOAP header)?
BR,
Jürgen

Answer 1

Jurgen
I have exactly the same problem in a RFC -> RFC Adapter -> XI -> SOAP Adapter -> Web Service scenario.
What we see is that the external vendor wants the SOAP to be in "documet-literal wrapped" whereas XI is returning is as "document literal".
**I don't want to change the original wsdl file because it was provided by our business partner and a modification could cause problems when release update.
But I have build a workaround with an XSL stylesheet as a second mapping step in my Interface Mapping. The stylesheet adds the missing operation tag into the XML message.**
Even in our case we dont want to change wsdl, the operation & soap body are going as two parts we want the soap body in operation,i think  this can be achieved by xsl stylesheet,Can u please brief us about xsl stylesheet as a second mapping step in interface maping.I dint work on xsl before......
Advance thanx for ur help
Sriram