Thanks, I downloaded this and looked over our headers.
For the WSDL file
They are set to text/plain. I have to admit that I have no clue what
this means, though my guess is that *no* interpretation is being done,
either html or xml.
The content (of the wsdl file) shows up as XML.
For the .wws file
Content-type is set to text/html
but what is being returned is definitely XML
So I am still confused about why the other party is getting encoded
results back.
On Dec 4, 2006, at 6:39 PM, Ben Johansen wrote:
If I had a URL i could do that,
So dale if you send me a URL i could test it for ya
Real quick
Ben
On Dec 4, 2006, at 3:33 PM, Robert Garcia wrote:
Try hitting your webservice, with something that gives you the RAW
out put, like my httptester or something. See what you get.
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/
On Dec 4, 2006, at 11:34 AM, Dale Graham wrote:
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
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
