AXL Documentation Inconsistencies

Version 1
    This document was generated from CDN thread

    Created by: Benjamin Kohl on 06-07-2011 08:40:36 AM
    I am developing an application that implements Cisco AXL and I am currently working from two sets of AXL documentation.  I have the WSDL and XSD files for CUCM 7.1 and I also have a single HTML file (axlapi.html) containing clickable images that lay out the schema also for CUCM 7.1.  These two schemas are not identical.  Many of the elements for "newPhone" that appear in one schema do not appear in the other.  Which schema is correct?  The axlapi.html or the XSD file (axlsoap.xsd)?

    Subject: RE: AXL Documentation Inconsistencies
    Replied by: Doug Kartio on 06-07-2011 08:49:20 AM
    I am using both those documents myself..  I tend to lean towards the WSDL, but have noticed inconsistencies.

    Can you give some examples of what you have noticed???

    Subject: RE: AXL Documentation Inconsistencies
    Replied by: Benjamin Kohl on 06-07-2011 08:57:34 AM
    For instance, in the HTML file, the "newPhone" object contains the following elements: name, protocol, product, model, class and protocolSide.  None of these elements can be found under "newPhone" in axlsoap.xsd.

    Subject: RE: AXL Documentation Inconsistencies
    Replied by: Doug Kartio on 06-07-2011 10:55:47 AM
    I never look at the XSD file anymore...

    Here is what I do.  Download a program called SoapUI.  There is a free version.  Open the WSDL file in SoapUI, then find the appropriate call (ex: addPhone), expand that level and click on the "Request 1", this then gives you EVERY possible field you could pass in.  You will have to weed out a lot of the garbage, but you will see what is needed.

    Normally, I go off the axlapi.html file and go to the SoapUI/WSDL file only if I have problems

    Hope that helps

    Subject: RE: AXL Documentation Inconsistencies
    Replied by: Benjamin Kohl on 06-07-2011 11:32:17 AM
    Microsoft Visual Studio Pro creates a pretty good graphical representation of XML schemas and I have been using that to drill down through AXL elements.