Cisco finally moves a bit in the WSDL arena

Question

I just downloaded the axlsql toolkit from my CCM 5.1 and it contains a wsdl + xsd file for Microsoft's wsdl.exe and Axis 1.4.
It still doesn't look as problem free as you have to make some changes in the stubs and the readme contains some passages that still scare me (The schema file AXLSoap.xsd is only for code generation and has been modified to enusure that future changes in the Database schema will cause minimum breakage to the code generated using WSDL and the schema files in the parent directory must be used for reference and for validation of response.) but that's a far cry from having to write your own xml statemens and parse the response on your own.
Seeing as changes still have to be made would indicate that the WSDL isn't autogenerated from the server implementation (if it were, there'd be at least one toolkit that could implement the WSDL without making any code changes.. and some wsdl generators can be told to create wsdl files using different approaches (e.g. the handling of arrays.. )) so we're still not where we ought to be, but at least something has been done.
The drawback here is that unless they're doing unit tests on those generated stubs, you'll run into unexplainable errors that will require that you debug the stub.

Answer 1

I was able to generate code using the wsdl.exe from .net 3.5 (pre-release). The wsdl and xsd files are from a CallManager 6.0(1) server.
"C:\Program Files\Microsoft SDKs\Windows\v6.0A\bin\wsdl.exe" /l:vb /o:axlapi.vb AXLAPI.wsdl axlsoap.xsd
I haven't tried to use it yet; there are some gotchas in the readme.