Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Problem in SOAP Request

Hi Experts,

I am working on SOAP-XI-Proxy Scenario. The Java system is using the WSDL from XI and triggering the following request

<?xml version="1.0" encoding="UTF-8" ?>

- <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

- <soapenv:Body>

- <SearchCustomer xmlns="urn:com.axonglobal.sbc.icase.customersearch">

<BPNo />

<Surname>Jones</Surname>

<FirstName />

<Phone />

<Email />

<PostCode />

<HouseNo />

<FlatNo />

<Street />

<Building />

<Estate />

</SearchCustomer>

</soapenv:Body>

</soapenv:Envelope>

But it receives the following error.

<?xml version="1.0" encoding="utf-8" ?>

- <!--

see the documentation

-->

- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

- <SOAP:Body>

- <SOAP:Fault>

<faultcode>SOAP:Server</faultcode>

<faultstring>Server Error</faultstring>

- <detail>

- <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">

<context>XIAdapter</context>

<code>MalformedMessageException</code>

- <text>

- <![CDATA[

Unexpected content in SOAP:Body; nested exception caused by:

com.sap.aii.messaging.util.XMLScanException: Unexpected content in SOAP:Body

at com.sap.aii.messaging.mo.Message.reparseRootDocument(Message.java:1014)

at com.sap.aii.messaging.net.MIMEInputSource.readSOAPPart(MIMEInputSource.java:619)

at com.sap.aii.messaging.net.MIMEInputSource.decodePart(MIMEInputSource.java:611)

at com.sap.aii.messaging.net.MIMEInputSource.readBody(MIMEInputSource.java:379)

u2026.

u2026u2026.

]]>

</text>

</s:SystemError>

</detail>

</SOAP:Fault>

</SOAP:Body>

</SOAP:Envelope>

IMP:- The call is not registered in the Message Monitoring at Adapetr Level or at Integration Engine Level, as I believe it is rejected as the Message Format is not correct .

Is it because , the request message is wrapped with the SOAP Envelope with the notation u2018<soapenv:Envelopeu2019 instead of the traditional u2018<SOAP:Envelopeu2019 notation?

We tested the same with XML Spy and it is working fine with the same payload.

Pls advise.

Regds.

Edited by: Subhendu Sahu on Apr 24, 2009 12:39 PM

Former Member

Helpful Answer

by
Not what you were looking for? View more on this topic or Ask a question