As a "side effect" of the work we have done to implement the Simple Web
Services API[1] we have set up a WSDL validator at:

   http://aspn.activestate.com/ASPN/WebServices/Tools/

Hope you might find it useful.

I ran the validator on the 128 unique WSDL URLs that are exposed at
XMethods [2] and 45% failed to pass the validator.  Of those that
fails, these are the reasons for failure:

  39%  HTTP GET fails (bad hostname, 404, timeout, html returned instead
       of WSDL, etc.)

  33%  Missing tns: prefix for internal references.  Why not simply
       skip putting a targetNamespace in the <definitions> ?

  12%  Messed up XML namespaces

   5%  Reference typos

   5%  Wrong order of top level elements

   4%  Missing type or element in <part> 

   2%  Attribute name typos

   2%  Nameless fault

   2%  Feature/limitation of the WSDL Validator:
         - will not read http from port 82.

Regards,
Gisle Aas,
ActiveState


[1] http://aspn.activestate.com/ASPN/WebServices/SWSAPI
[2] http://www.xmethods.net/sd/2001/XMethodsListingsService.wsdl

------------------------ Yahoo! Groups Sponsor ---------------------~--> 
Win a Capcom Console Game of Your Choice Or Even a Capcom Arcade System. Click Here to Enter
.
http://us.click.yahoo.com/tmpz8B/exbDAA/ySSFAA/W6uqlB/TM
---------------------------------------------------------------------~-> 

To unsubscribe from this group, send an email to:
wsdl-unsubscribe@[...].com

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/