Axis1.4 Client Stub Problem

Version 1
    This document was generated from CDN thread

    Created by: Shahzad Munir on 08-05-2009 05:19:13 AM
    I am trying to communicate with CUCM using AXL. For this purpose I have opted Axis to create client stub. Client is generated successfully but I am facing problem running this client code. After removing known bugs mentioned in CUCM 6.X Development Guide.pdf à Using the AXL API with AXIS section, I tried to call service function getPhone() but having exception (stack trace given below):
     
     
    AxisFault
     faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
     faultSubcode:
     faultString: org.xml.sax.SAXException: Invalid element in com.wateen.cucm.client.ws.axl.types.XLine - recordingFlagName
     faultActor:
     faultNode:
     faultDetail:
          {http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXException: Invalid element in com.wateen.cucm.client.ws.axl.types.XLine - recordingFlagName
          at org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeserializer.java:258)
          at org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1035)
          at org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:165)
          at org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1141)
          at org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236)
          at org.apache.axis.message.RPCElement.getParams(RPCElement.java:384)
          at org.apache.axis.client.Call.invoke(Call.java:2467)
          at org.apache.axis.client.Call.invoke(Call.java:2366)
          at org.apache.axis.client.Call.invoke(Call.java:1812)
          at com.wateen.cucm.client.ws.axl.serv.AXLAPIBindingStub.getPhone(AXLAPIBindingStub.java:11441)
          at com.wateen.cucm.test.CucmAxlTest.main(CucmAxlTest.java:61)
     
          {http://xml.apache.org/axis/}hostname:wlhe-arg-it2224
     
    org.xml.sax.SAXException: Invalid element in com.wateen.cucm.client.ws.axl.types.XLine - recordingFlagName
          at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
          at org.apache.axis.client.Call.invoke(Call.java:2470)
          at org.apache.axis.client.Call.invoke(Call.java:2366)
          at org.apache.axis.client.Call.invoke(Call.java:1812)
          at com.wateen.cucm.client.ws.axl.serv.AXLAPIBindingStub.getPhone(AXLAPIBindingStub.java:11441)
          at com.wateen.cucm.test.CucmAxlTest.main(CucmAxlTest.java:61)
    Caused by: org.xml.sax.SAXException: Invalid element in com.wateen.cucm.client.ws.axl.types.XLine - recordingFlagName
          at org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeserializer.java:258)
          at org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1035)
          at org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:165)
          at org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1141)
          at org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236)
          at org.apache.axis.message.RPCElement.getParams(RPCElement.java:384)
          at org.apache.axis.client.Call.invoke(Call.java:2467)
     
     
    Complex type XLine in the WSDL-AXIS/AXLSoap.xsd has element with name recordingFlag and not recordingFlagName. As a work-around I updated following line in XLine.java from
    elemField.setXmlName(new javax.xml.namespace.QName("", "recordingFlag")); (line 995)
          to
    elemField.setXmlName(new javax.xml.namespace.QName("", "recordingFlagName"));
     
    This should have fixed the problem but now new exceptions were thrown:
     
     
    AxisFault
     faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
     faultSubcode:
     faultString: org.xml.sax.SAXException: Invalid element in com.wateen.cucm.client.ws.axl.types.XIPPhone - primaryPhoneName
     faultActor:
     faultNode:
     faultDetail:
          {http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXException: Invalid element in com.wateen.cucm.client.ws.axl.types.XIPPhone - primaryPhoneName
          at org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeserializer.java:258)
          at org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1035)
          at org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:165)
          at org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1141)
          at org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236)
          at org.apache.axis.message.RPCElement.getParams(RPCElement.java:384)
          at org.apache.axis.client.Call.invoke(Call.java:2467)
          at org.apache.axis.client.Call.invoke(Call.java:2366)
          at org.apache.axis.client.Call.invoke(Call.java:1812)
          at com.wateen.cucm.client.ws.axl.serv.AXLAPIBindingStub.getPhone(AXLAPIBindingStub.java:11441)
          at com.wateen.cucm.test.CucmAxlTest.main(CucmAxlTest.java:61)
     
          {http://xml.apache.org/axis/}hostname:wlhe-arg-it2224
     
    org.xml.sax.SAXException: Invalid element in com.wateen.cucm.client.ws.axl.types.XIPPhone - primaryPhoneName
          at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
          at org.apache.axis.client.Call.invoke(Call.java:2470)
          at org.apache.axis.client.Call.invoke(Call.java:2366)
          at org.apache.axis.client.Call.invoke(Call.java:1812)
          at com.wateen.cucm.client.ws.axl.serv.AXLAPIBindingStub.getPhone(AXLAPIBindingStub.java:11441)
          at com.wateen.cucm.test.CucmAxlTest.main(CucmAxlTest.java:61)
    Caused by: org.xml.sax.SAXException: Invalid element in com.wateen.cucm.client.ws.axl.types.XIPPhone - primaryPhoneName
          at org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeserializer.java:258)
          at org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1035)
          at org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:165)
          at org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1141)
          at org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236)
          at org.apache.axis.message.RPCElement.getParams(RPCElement.java:384)
          at org.apache.axis.client.Call.invoke(Call.java:2467)
          ... 4 more
     
     
    primaryPhone and primaryPhoneName are there in the AXL_API_Interface_Spec document but no such element in WSDL-AXIS/AXLSoap.xsd. Based on AXL_API_Interface_Spec document, I introduced both these attributes in the hierarchy (XIPPhoneàXPhoneàXDevice). Now code gives some Invalid Positive Integer error.
     
    It seems that Schema and WSDL files in the axlsqltoolkit.zip are different from actual ones which are being used by the AXL Service. PS I have download axlsqltoolkit.zip from the same server I am trying to communicate with.

    Am I doing something wrong? Kindly help out

    Subject: RE: Axis1.4 Client Stub Problem
    Replied by: Anitha V on 08-05-2009 07:25:01 AM
    Hi Shahzad,
     
    Looks like schema mismatch.
     
    Could you please let me know which UCM version you are using? Are you using http://IPADDRESS/emapp/EMAppServlet?device=#DEVICENAME#
    in your getPhone() request
     
    Thanks and Regards,
    Anitha

    Subject: RE: Axis1.4 Client Stub Problem
    Replied by: Shahzad Munir on 13-05-2009 10:00:57 AM
    You are right. This must be a schema mismatch. CUCM Version I am trying to communicate with is : CUCM 6.0.1.2000-3
    But I am failed to understand why this is happening for I have downloaded axlsqltoolkit.zip from the same server I am trying to communicate with using AXL.

    Are you using http://IPADDRESS/emapp/EMAppServlet?device=#DEVICENAME# in your getPhone() request
     
    I couldnt get what you are trying to ask. I am placing my request at: https://IPADDRESS:8443/axl/

    Thanks Anitha

    Subject: RE: Axis1.4 Client Stub Problem
    Replied by: Anitha V on 13-05-2009 11:43:55 AM
    Hi Shahzad,
     
    Could you please send the exact AXL request and the response and the corresponding AXL logs for further analysis?
     
    Thanks
    Anitha