Note that there are some explanatory texts on larger screens.

plurals
  1. PO.net Client consuming Axis2 Web Service
    primarykey
    data
    text
    <p>I have an .net 2.0 <strong>C#</strong> client app that has a web service reference to an <strong>Axis2</strong> Java Webservice. The idea is to send some xml data to the webservice, so it can be parsed and inserted into database. The WS method accepts a single parameter of type 'xsd:anytype'.</p> <p>Java web service:</p> <pre><code>public class JWS{ public Response AddData(Object inputXML) { return Response; } } </code></pre> <p>C# Client:</p> <pre><code>JWS client = new JWS(); object inputXML = "&lt;xml&gt;some xml data&lt;/xml&gt;"; response = client.AddData(inputXML); </code></pre> <p>There are 2 issues i am seeing when monitored using fiddler.</p> <p>1) The request has an additional element <code>'&lt;inputXML&gt;'</code> added before the actual xml data.</p> <pre><code>&lt;inputXML&gt;&amp;lt;xml&amp;gt;some xml data&amp;lt;/xml&amp;gt;&lt;/inputXML&gt; </code></pre> <p>2) The xml is encoded, so '&lt;' is appearing as <code>"&amp;lt;"</code></p> <p>I am not sure if this is how SOAP request's are generated but i would like to remove the <code>&lt;inputXML&gt;</code> tag and also, have the xml appear as is without having to replace the special characters.</p> <p>Is this possible? Is it got something to do with 'Wrapping'/'UnWrapping' Types?</p> <p>Also, i have used SoapUI to test the java web service and it works well. However, in the request tab, i had to manually remove the <code>&lt;inputXML&gt;</code> tag and submit for it to work correctly. Please help.</p> <p>TIA</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

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