Due to many shortcomings of the webMethods Developer WSDL generator, I and others have advised developers to create WSDL files using alternate tools such as XML Spy Enterprise or the Eclipse WDT WSDL editor. I personally use XML Spy because it does a better job of validating WSDL files up front.
I expected to find these tools to be valuable in building web services regression test suites and, so far, it looks as if this will be true.
What I did not expect was that these tools also add value by performing interoperability testing of WSDL files that were created using XML Spy, Eclipse WDT or (yech) webMethods Developer WSDL generator.
Both tools utilize the WS-I’s interoperability test suite to measure the degree to which a WSDL meets the best practice recommendations. SOAP Sonar only provides one type of WS-I test while SOAPScope allows you to choose from several. Both tools have trouble pinpointing the exact location inside the WSDL file that is causing a WS-I “violation” to be reported.
At any rate, using one of these tools or a similar one helps to identify issues in a project’s WSDL files that might need to be addressed in order to improve its interoperability with the service’s consumers.
My feature request for WM is to add the ability to measure WS-I compliance into whatever WSDL generation will be provided in the next major release of IS. Doing so will not only be useful for developers, but putting it in the product will likely lead to higher quality of generated WSDL’s.