I know that this has come up in this forum before, but I'm hoping some kind soul can help me revisit this issue and get it solved.
Microsoft's wsdl.exe tool (used to consume a WSDL file and generate a client proxy for the web service) errors out on AXLAPI.wsdl. I think it is in the way that dependent XSD files are imported/included.
Here is the output when you enter:
wsdl axlapi.wsdl
Microsoft (R) Web Services Description Language Utility
[Microsoft (R) .NET Framework, Version 1.1.4322.915]
Copyright (C) Microsoft Corporation 1998-2002. All rights reserved.
Error: Unable to import binding 'AXLAPIBinding' from namespace 'http://www.cisco.co
m/AXLAPIService/'.
- Unable to import operation 'addPhone'.
- The element 'http://www.cisco.com/AXL/API/1.0:addPhone' is missing.
I've tried various things. An MS article (http://support.microsoft.com/default.aspx?scid=kb;en-us;820122) seemed to be a lead. The work around is to edit the files (the WSDL and referenced schema files) a bit. But I couldn't come up with the right combination. I will tell you that if you add arguments to the wsdl command, you get different messages. For example:
wsdl AXLAPI.WSDL axlsoap.xsd axl.xsd
Microsoft (R) Web Services Description Language Utility
[Microsoft (R) .NET Framework, Version 1.1.4322.915]
Copyright (C) Microsoft Corporation 1998-2002. All rights reserved.
Error: Unable to import binding 'AXLAPIBinding' from namespace 'http://www.cisco.co
m/AXLAPIService/'.
- Unable to import operation 'addPhone'.
- These members may not be derived.
I really don't want to have to roll my own SOAP/HTML to talk to the AXL api. If I can get the proxy to generate, .NET makes the rest a piece of cake. But this has stymied me so far.
Thanks for any and all help.
