cancel
Showing results for 
Search instead for 
Did you mean: 

Namespaces in SOAP Message

Former Member
0 Kudos

Hi,

we have a RFC->XI->SOAP scenario. Until now everything worked fine. However, I received a new WSDL which I imported into Integration Builder. After that I updated all interfaces and message mappings. Now the WebServices Server cannot process my requests anymore. It throws an exception because of unknown elements.

Here an example of the message when calling the SOAP adapter:

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

- <ns0:Document__SOAP_NameRequest xmlns:ns0="http://www.xxx.ag/xxxsoap">

<ns0:docid>0000000000000000000142632</ns0:docid>

</ns0:Document__SOAP_NameRequest>

And here the error in the protocol of the WebServices server:

SOAPService::SOAPParse - <SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'><SOAP:Header/><SOAP:Body><ns0:Document__SOAP_NameRequest xmlns:ns0='http://www.xxx.ag/xxxsoap'><ns0:docid>0000000000000000000142632</ns0:docid></ns0:Document__SOAP_NameRequest></SOAP:Body></SOAP:Envelope>

XML String : <SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'><SOAP:Header/><SOAP:Body><ns0:Document__SOAP_NameRequest xmlns:ns0='http://www.xxx.ag/xxxsoap'><ns0:docid>0000000000000000000142632</ns0:docid></ns0:Document__SOAP_NameRequest></SOAP:Body></SOAP:Envelope>

Error:

[Fri Sep 02 16:03:03 2005] Exception: SOAPService - XML data error: unknown type at element ns0:docid

Obviously the server has a problem with the ns0. Now, I'm not sure if this is really a problem with the server. Or if XI cut the ns0 off before...

Can anybody help with this problem?

Regards,

Carmen

Accepted Solutions (0)

Answers (1)

Answers (1)

stefan_grube
Active Contributor
0 Kudos

Hi Carmen,

for me it looks like, there is a problem with the value 0000000000000000000142632.

There are 25 digits. Is this, was the server expects?

The SOAP adapter does touch the payload in any way, so you can be assured, that you receive the same as you send out.

Regards

Stefan

Former Member
0 Kudos

Hi Stefan,

No, the value cannot be the problem, because the server converts this string into an integer anyway. And it worked with this value before.

Carmen