umm.. am I blind? I thought I had just posted here.
Anyway.. with CCM 5.1.1 you get a WSDL that you can import with AXIS 1.4 and wsdl.exe. With earlier versions, you're off to some manual hacking on your own.
I didn't write the webserver plugin for AXL, but I suspect the reason for this whole mess is the following: instead of using a webservice toolkit, Cisco simply wrote their own (ISAP for CCM 4.x) plugin that goes through requests line by line and analyzes them.. everything done manually. It doesn't even validate XML and in CCM 5.0.4 you can send invalid XML data (including corrupt AXL requests) to the CCM and it will be processed (in many cases you even get information back.. e.g. you can mix getphone and getline and you get a valid getphone response)) and it will get you a valid response (other than "incorrect xml"). This would also explain why the order of the xml elements is crucial.. if they had a regular webservice framework, the order would not matter as elements would be extracted from a request via dom/xquery lookups (that's how my own axl framework does it.. both require xml validation so any invalid xml axl would return would immediately trigger an error.. on the other hand, switched element order doesn't matter to my framework).
With that in mind, it's clear that every WSDL file is hand written and unless they start from scratch with a webservice capable framework (I suspect it's written in C(++) so it's not as simply as copying and pasting code into java files and have the whole thing run as a tomcat app and use JAX to export the WSDL file), AXL will continue to be a mess.
