|
next
|
Subject: WSDL - A Well Defined Service Author: taylor corey Date: 03 Jan 2008 02:40 AM
|
I have a customer who claims their web service (and WSDL and schema files) are being used successfully by .net and java clients.
I tried their WSDL file at soapclient.com and generated a request message. The SOAP message had nothing in the body, so, I tried the same thing in Stylus Studio and it had fields in the SOAP body but when I tried to assign values, Stylus Studio said the fields are not accessible and a namespace is undefined.
After looking long and hard, I inserted a namespace in the WSDL file and generated a web service call. The SOAP message had the fields and I could assign values to them.
I went back and tried the WSDL file in soapclient.com and the same problem occurred (yes, I selected no caching), the SOAP body was empty.
After all this, I concluded the web service is not well defined. Given that a well defined web service describes exactly what messages need to be sent, how is it that soapclient.com, Stylus Studio, and other WSDL validators can return different results, some appear correct, some not, etc.? In other words, what part of the W3C proposals allow for this kind of variation?
Thanks.
-t
|
|
|
|