Missing wsdl and xsd files for .NET in AXL version 8.0

Version 1
    This document was generated from CDN thread

    Created by: Robert Kolb on 27-08-2010 01:06:07 PM
    Hi

    I am developing an application using .NET to access CUCM via AXL. For all the CUCM versions below 8, specific xsd and wsdl files for .NET have been provided in the AXL-SQL-Toolkit and have been used with success.
    However, version 8.0(2) lacks of these specific files. I tried to uses the files AXLAPI.wsdl and AXLSoap.xsd in the schema\8.0 directory of the AXL-SQL-Toolkit but failed to generate the csharp proxy classes with the .NET wsdl.exe compiler.

    Issuing the command to compile the wsdl/xsd files, the following error is displayed:

    D:\Home\Work\GenAXLProxy\8.0>"C:\Program Files\Microsoft SDKs\Windows\v6.1\Bin\wsdl.exe" AXLAPI.wsdl axlsoap.xsd
    Microsoft (R) Web Services Description Language Utility
    [Microsoft (R) .NET Framework, Version 2.0.50727.1432]
    Copyright (C) Microsoft Corporation. All rights reserved.
    Error: Unable to import binding 'AXLAPIBinding' from namespace 'http://www.cisco.com/AXLAPIService/'.
      - Unable to import operation 'addTimeSchedule'.
      - These members may not be derived.

    If you would like more help, please type "wsdl /?".

    D:\Home\Work\GenAXLProxy\8.0>


    It seams, that the wsdl/xsd files are not compatible with .NET

    Now my question:
    How can I generate the csharp .NET proxy classes for AXL Version 8.0?

    Subject: RE: Missing wsdl and xsd files for .NET in AXL version 8.0
    Replied by: Erik Briggs on 15-02-2011 06:22:35 PM
    I am running into similar issues here.  The version 8.0 wsdl and xsd files are not documented and are totally different from version 7 and back.  We are upgrading to 8 from 4.1, so all of my custom software I need to modify to use AXL, but none of the sample code works, because of all the changes to the 8.0 API.  Does anyone have any ideas or has some sample code that works with the 8.0 API?  Thanks.

    Subject: RE: Missing wsdl and xsd files for .NET in AXL version 8.0
    Replied by: Gordon Ross on 16-02-2011 01:27:08 AM
    The big change in V8.0 of the AXL APIs is that they changed the capitalisation standard for everything. e.g. AARGroup (V7) changes to AarGroup (V8).

    GTG

    Subject: RE: Missing wsdl and xsd files for .NET in AXL version 8.0
    Replied by: Erik Briggs on 16-02-2011 03:13:22 PM
    Well, based on the fact that the 8.0 API is missing many methods and functions that exist in previous versions, it seems like Cisco isn't really trying to support it that much.  That may because of the CUAE having its own DLL files with all those functions rolled in with an IDE.  It may be their intention to try and move people to there, instead of allowing people from rolling their own. 

    I solved my issues by trying the 7.1 API.  The main problem I found was that the updateLine function in the 8.0 API doesn't work, because there is no pattern field.  The "newPattern" field doesn't replace it, so therefore it is unuseable for what I was trying to do (update call forwards).  I stumbled onto CUAE and started using the Metreos DLL files instead, but those seemed to be very similar to the AXLAPIService.cs file I was creating for 7.1 and 8.0 on my own.  There are many other functions are missing compared the older versions.  This is distressing because the API matrix shows that it should contain those methods.

    I wish some of this stuff was better documented so I didn't feel like Cisco was leaving me hanging out to dry on my own.

    Subject: RE: Missing wsdl and xsd files for .NET in AXL version 8.0
    Replied by: Gordon Ross on 17-02-2011 01:05:46 AM
    I wish some of this stuff was better documented so I didn't feel like Cisco was leaving me hanging out to dry on my own.

     
    You and me both...

    Subject: RE: Missing wsdl and xsd files for .NET in AXL version 8.0
    Replied by: Gordon Ross on 17-02-2011 01:08:58 AM
    I wish some of this stuff was better documented so I didn't feel like Cisco was leaving me hanging out to dry on my own.

     
    You and me both...