Note that there are some explanatory texts on larger screens.

plurals
  1. POSoap web service and android client using ksoap protocal mismatch
    primarykey
    data
    text
    <p>I have and android client, that uses ksoap to communicate with a wsdl web service written in c# asp.net. I have a problem with matching the argument types between the web service and the client. The web server expects to this kind of request (auto generated):</p> <pre><code>&lt;?xml version="1.0" encoding="utf-8"?&gt; &lt;soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"&gt; &lt;soap:Body&gt; &lt;GetDetails xmlns="http://host.org/"&gt; &lt;event_id&gt;int&lt;/event_id&gt; &lt;/GetDetails&gt; &lt;/soap:Body&gt; &lt;/soap:Envelope&gt; </code></pre> <p>the client sends requests using ksoap, and they look like this:</p> <pre><code>&lt;v:Envelope xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns:d="http://www.w3.org/2001/XMLSchema" xmlns:c="http://schemas.xmlsoap.org/soap/encoding/" xmlns:v="http://schemas.xmlsoap.org/soap/envelope/"&gt; &lt;v:Header /&gt; &lt;v:Body&gt; &lt;n0:GetDetails id="o0" c:root="1" xmlns:n0="http://tempuri.org"&gt; &lt;event_id i:type="d:int"&gt;1&lt;/event_id&gt; &lt;/n0:GetDetails&gt; &lt;/v:Body&gt; &lt;/v:Envelope&gt; </code></pre> <p>For some reason the WS parses the following' client's request as 0 (I guess because of the additional type attributes - i:type="d:int") when the request is assembled manually to look like the first option, it works correctly. How can i make the web service read the ksoap format correctly or how can i change it's expected format to look like ksoap request. (the web service soap protocol is auto generated).</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.
 

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