Note that there are some explanatory texts on larger screens.

plurals
  1. PO.net create custom request and response for web service?
    text
    copied!<p>I am doing an integration where I have to consume 3rd party java based web service. This 3rd party web service is highly case sensitive. After adding the web service to the .net project. We called there methods. But .net code creates its own Request XML which is different then the XML needed by the vendor.</p> <p>For example .net creates XML as Follows</p> <pre><code>&lt;s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"&gt; &lt;s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"&gt; &lt;GetAccountBalanceRequest xmlns="http://www.XXXXXXX.com/lmsglobal/ws/v1/extint/types"&gt; &lt;Authentication&gt; &lt;Principal xmlns="http://www.XXXXXXX.com/lmsglobal/xsd/v1/types"&gt; &lt;PrincipalValue&gt;9401120106480306&lt;/PrincipalValue&gt; &lt;PrincipalClassifier&gt;0001&lt;/PrincipalClassifier&gt; &lt;/Principal&gt; &lt;Credential xmlns="http://www.XXXXXXX.com/lmsglobal/xsd/v1/types"/&gt; &lt;/Authentication&gt; &lt;LoyaltyCurrency xsi:nil="true"/&gt; &lt;/GetAccountBalanceRequest&gt; &lt;/s:Body&gt; </code></pre> <p> </p> <p>But the vendor say they want XML as Follows</p> <pre><code>&lt;soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://www.XXXXXXX.com/lmsglobal/ws/v1/extint/types" xmlns:typ1="http://www.XXXXXXX.com/lmsglobal/xsd/v1/types"&gt; &lt;soapenv:Header/&gt; &lt;soapenv:Body&gt; &lt;typ:GetAccountBalanceRequest&gt; &lt;typ:Authentication&gt; &lt;typ1:Principal&gt; &lt;typ1:PrincipalValue&gt;9401120106480306&lt;/typ1:PrincipalValue&gt; &lt;typ1:PrincipalClassifier&gt;0001&lt;/typ1:PrincipalClassifier&gt; &lt;/typ1:Principal&gt; &lt;/typ:Authentication&gt; &lt;/typ:GetAccountBalanceRequest&gt; &lt;/soapenv:Body&gt; &lt;/soapenv:Envelope&gt; </code></pre> <p>How do I modify the web service so it will generate Request XML as vender needs?</p> <p>I used Soap UI also for checking the response. If I use .net generated XML then it fails but I use the above XML then it works.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload