Quantcast
Channel: SCN: Message List - Service-Oriented Architecture (SOA) and SAP
Viewing all articles
Browse latest Browse all 1056

Consume Webservice using ABAP client proxy : Issue with name space

$
0
0

Hi All,

 

We are trying to consume a web service published by a third party. For that we have created a consumer proxy and logical port in SOAMANAGER. Also we have added custom SOAP header since the header generated by SAP is not in a format understandable by the service provider.

 

We are getting a SOAP fault exception while trying to invoke the service from SAP system. However we were successful in testing the web service using SOAP UI testing tool. The difference in the requests generated by SAP and SOAP UI is the location of namespace definitions in the SOAP requests. In the request generated by SOAP UI, all the namespace definitions are at Envelope level (just after soap-env:Envelope). We tested the request generated by SAP in SOAP UI testing tool and got the same error. So we edited the same request using SOAP UI and copied all the namespace definitions from SOAP body and pasted it just after soap-env:Envelope like the one shown below and it gave us the correct results.

 

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

xmlns:nm="XXXXX"

xmlns:prx="XXXXX"

xmlns:ne="XXXXX"

xmlns:n0="XXXXX">

<soap-env:Header>

 

Would it be possible to change the SOAP request once it is generated so that we can pass all the namespace definitions just after <soap-env:Envelope or is there any other way to pass the namespace definition at envelope level to solve this problem.

 

Could you please share your thoughts and ideas on this.

 

Regards,

Arun


Viewing all articles
Browse latest Browse all 1056

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>