Mapping issues with soap sender adapter

[Former Member]

Scenario SOAP->XI-> file.

I have configured a sender soap adapter.

When the soap message is sent to XI from third party system using the 'DOC' , SXMB_MONI shows the following format

<SOAP-ENV:Envelope

xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"

xmlns:xs="http://www.w3.org/2001/XMLSchema"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xmlns:m="http://localhost">

<SOAP-ENV:Body>

<m:MyOperation>

<b> <m:a>123</m:a>

<m:b>abc</m:b></b> </m:MyOperation>

</SOAP-ENV:Body>

</SOAP-ENV:Envelope>

But I get a mapping exception..

While the soap message generated through XMLSPY, is processed successfully. The main difference that I can see between the two soap request, "The namespace M: is getting attached to the failed soap request". I have highlighted the difference. How should I handle this?

<SOAP-ENV:Envelope

xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"

xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"

xmlns:xs="http://www.w3.org/2001/XMLSchema"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

>

<SOAP-ENV:Body>

<m:MyOperation xmlns:m="http://localhost">

<b> <a>123</a>

<b>abc</b></b>

</m:MyOperation>

</SOAP-ENV:Body>

</SOAP-ENV:Envelope>

[moorthy]

Hi,

Are you using XSL mapping for the Same ? If so try to add the NameSpace in the Header. like <xmlns:....Name Space Name/>

Otherwise avoid the Namespace from your message. That can be done while creating the Message Type.

Hope this helps..

Regards,

Moorthy

[Former Member]

Krishna,when the soap client uses 'RPC', namespace is not part of the soap request and it works. When they use 'DOC', namespace is included as part of the soap request and mapping fails.

Is there something i can do to conversion parameters to handle this?