We supply a webservice to another group, and all of a sudden, they
ran into some problems with it.
One of the problems was that they were getting back the data as
encoded...
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/
envelope/">
<soap:Body>
<approvers_Response xmlns="witangowebservices">
<approverdata></approverdata>
<sddata></sddata>
<status></status>
</approvers_Response>
</soap:Body>
</soap:Envelope>
So I told them that I thought they should be including Content-type:
text/xml in the http header - when I do so, I get XML, not encoded HTML
Then they fired back the following:
-------
If we talk about SOAP web service we have to stick to SOAP
specifications.
This is the main reason of web services. Data can be transfered in
heterogeneous environment.
I use main stream tools from Microsoft. And I have a significant part
of automatically generated code which is supposed to support the
standards, and I hardly want to rewrite it. Of cause the tools have
their own bugs but it is wrong idea to override the standards.
-------
And here I thought the use of Content-type *was* the standard. I
personally think that someone who's using Microsoft tools (.NET,
wsdl.exe) is on very shaky grounds here... and that he's wrong. Or am
I in error?
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
