norman.walsh.name: Comments on /2005/02/24/wsdlhttp://norman.walsh.name/2005/02/24/wsdl/comments.atom2012-02-13T04:06:07.514989ZComment 1 on /2005/02/24/wsdlhttp://norman.walsh.name/2010/09/25/oauth#comment00012005-02-25T03:40:04Z2005-02-25T03:40:04ZDavid Megginsonda39a3ee5e6b4b0d3255bfef95601890afd80709

I sympathize -- I had to figure out WSDL well enough to write some examples in my book, and it wasn't a fun task.

Comment 2 on /2005/02/24/wsdlhttp://norman.walsh.name/2010/09/25/oauth#comment00022005-02-25T16:16:25Z2005-02-25T16:16:25ZShifra Raffelda39a3ee5e6b4b0d3255bfef95601890afd80709

Two checkers that might be handy if you haven't already tried them on your WSDL: http://www.mindreef.net/tide/scopeit/start.do and http://soapclient.com/soaptest.html. Thanks for letting us all in on your experiments!

Comment 3 on /2005/02/24/wsdlhttp://norman.walsh.name/2010/09/25/oauth#comment00032005-02-25T19:06:30Z2005-02-25T19:06:30ZSavas Parastatidisda39a3ee5e6b4b0d3255bfef95601890afd80709

You may find this WS description language interesting... no great tool support i am afraid but we hope it's easier than WSDL...

http://ssdl.org

Comment 4 on /2005/02/24/wsdlhttp://norman.walsh.name/2010/09/25/oauth#comment00042005-03-01T06:45:34Z2005-03-01T06:45:34ZJames Fullerda39a3ee5e6b4b0d3255bfef95601890afd80709

sometimes...when people are not looking....i use RDDL to define and describe my REST type web services....

I find WSDL is, like the rest of the WS stack, overblown for anything less then enterprise type development....if need be I would suggest using XML Spy to create a nice WSDL document....when I made them for various books, etc...