I've got this annoying problem:
On the server's side there's an Apache w/ PHP running. I wrote a kind of
"bare bones" SOAP implementation, though meeting the SOAP specs. Afaics
this part isn't causing the problem.
To be able to use wsdl.exe, I've tried to describe my web service wie a
WSDL file. I will post this file as soon as an expert is willing to care
for my troubles and asks me to do so, since the file is of course kind
of lengthy. To find a hook to get on the right trace, I've told my PHP
script to write the .NET client app's requests into a log file. This
file, though, is witnessing the garbage the client app is producing:
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:tns="..."
xmlns:types="..."
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Body soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> <xsd:int xsi:type="xsd:int">1</xsd:int>
</soap:Body>
</soap:Envelope>
The lines marked with ">"s are, of course, just nonesense. A correct
request would look like:
<soap:Body xmlns:m="Meins">
<m:GetUser>
<m:UserID>1</m:UserID>
</m:GetUser>
</soap:Body>
The WSDL file contains:
<message name="GetUser">
<part name="UserID" type="xsd:int" />
</message>
I've tried to use types before, but wsdl.exe refused to create
appropriate code with a message about a non-existent type definition. Of
course, first I tought I made a mistake, but then I tried an example
WSDL file from http://www.w3.org/TR/wsdl#_rpcexample. wsdl.exe carped
about the same stuff (non-existent type-defs). Because of that, I
switched to XMLSchema types. But since then, wsdl.exe is producing the
described rubbish.
What am I doing wrong??? Any hint??? Thx in advance!
Regards from Germany,
Carsten
