You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Liron Raveh (JIRA)" <ji...@apache.org> on 2008/06/02 10:33:45 UTC
[jira] Commented: (AXIS2-3259) ADBException: Unexpected subelement
contentType
[ https://issues.apache.org/jira/browse/AXIS2-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601551#action_12601551 ]
Liron Raveh commented on AXIS2-3259:
------------------------------------
I'm also getting this problem with Axis2 1.3 without using base64. It doesn't happen all the time, one one response it can on the other it doesn't: Here is the stack trace:
org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException: Unexpected subelement causeCode
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417)
at com.vocaltec.casiopea.webservices.exmonitor.EXMonitorServiceEXMonitorPortStub.fromOM(EXMonitorServiceEXMonitorPortStub.java:1434)
at com.vocaltec.casiopea.webservices.exmonitor.EXMonitorServiceEXMonitorPortStub.getHistoricalCalls(EXMonitorServiceEXMonitorPortStub.java:976)
at com.vocaltec.casiopea.webservices.exmonitor.client.MyEXMonitorStub.getHistoricalCalls(MyEXMonitorStub.java:69)
at com.vocaltec.casiopea.webservices.exmonitor.client.EXMonitorDataHandler.getAndSetCallRecordsByWebservice(EXMonitorDataHandler.java:157)
at com.vocaltec.casiopea.webservices.exmonitor.client.EXMonitorDataHandler.getPageResults(EXMonitorDataHandler.java:113)
at _casiopea._webservices._exmonitor._GetCallLists._jspService(_GetCallLists.java:184)
[SRC:/casiopea/webservices/exmonitor/GetCallLists.jsp:80]
at com.orionserver[Oracle9iAS (9.0.2.1.0) Containers for J2EE].http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:302)
at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:407)
at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:330)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:336)
at com.evermind[Oracle9iAS (9.0.2.1.0) Containers for J2EE].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:696)
at com.evermind[Oracle9iAS (9.0.2.1.0) Containers for J2EE].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:281)
at com.evermind[Oracle9iAS (9.0.2.1.0) Containers for J2EE].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:766)
at com.evermind[Oracle9iAS (9.0.2.1.0) Containers for J2EE].server.http.HttpRequestHandler.run(HttpRequestHandler.java:259)
at com.evermind[Oracle9iAS (9.0.2.1.0) Containers for J2EE].server.http.HttpRequestHandler.run(HttpRequestHandler.java:107)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:802)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.Exception: org.apache.axis2.databinding.ADBException: Unexpected subelement causeCode
at com.vocaltec.sim.sip.services.monitoring.xsd.WSCallLeg$Factory.parse(WSCallLeg.java:1610)
at com.vocaltec.sim.sip.services.monitoring.xsd.WSCallRecord$Factory.parse(WSCallRecord.java:902)
at com.vocaltec.sim.webservices.exmonitor.GetHistoricalCallsResponse$Factory.parse(GetHistoricalCallsResponse.java:530)
at com.vocaltec.casiopea.webservices.exmonitor.EXMonitorServiceEXMonitorPortStub.fromOM(EXMonitorServiceEXMonitorPortStub.java:1393)
... 17 more
Caused by: org.apache.axis2.databinding.ADBException: Unexpected subelement causeCode
at com.vocaltec.sim.sip.services.monitoring.xsd.WSCallLeg$Factory.parse(WSCallLeg.java:1604)
... 20 more
Is this a bug or i'm doing something wrong?
This relevant part on the wsdl:
<xs:element name="getHistoricalCalls">
<xs:complexType>
<xs:sequence>
<xs:element name="callingPartyNumber" minOccurs="0" type="xs:string" nillable="true"/>
<xs:element name="callingPartyType" minOccurs="0" type="xs:string" nillable="true"/>
<xs:element name="calledPartyNumber" minOccurs="0" type="xs:string" nillable="true"/>
<xs:element name="calledPartyType" minOccurs="0" type="xs:string" nillable="true"/>
<xs:element name="origEndpoint" minOccurs="0" type="xs:string" nillable="true"/>
<xs:element name="termEndpoint" minOccurs="0" type="xs:string" nillable="true"/>
<xs:element name="maxRecords" minOccurs="0" type="xs:int"/>
<xs:element name="unsuccessfulOnly" minOccurs="0" type="xs:boolean"/>
<xs:element name="causeCode" minOccurs="0" type="xs:string" nillable="true"/>
<xs:element name="causeCodeType" minOccurs="0" type="xs:string" nillable="true"/>
</xs:sequence>
</xs:complexType>
</xs:element>
> ADBException: Unexpected subelement contentType
> -----------------------------------------------
>
> Key: AXIS2-3259
> URL: https://issues.apache.org/jira/browse/AXIS2-3259
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: adb
> Affects Versions: 1.3
> Environment: WSDL2java generated client
> Reporter: Etienne
> Assignee: Amila Chinthaka Suriarachchi
> Attachments: knowledgebase.tar, KnowledgeBaseService.wsdl, request.xml, response.xml, soapbody.xml, tcp-session-parsing-KO.txt, tcp-session-parsing-OK.txt
>
>
> With axis2 I have an issue with a complex type containing a
> base64Binary element:
> <xsd:complexType name="BinaryFile">
> <xsd:sequence>
> <xsd:element minOccurs="0" name="content" nillable="true"
> type="xsd:base64Binary"/>
> <xsd:element minOccurs="0" name="contentType" nillable="true"
> type="xsd:string"/>
> <xsd:element minOccurs="0" name="id" type="xsd:int"/>
> <xsd:element minOccurs="0" name="name" nillable="true" type="xsd:string"/>
> </xsd:sequence>
> </xsd:complexType>
> When the client fails with the following exception;
> org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException:
> Unexpected subelement contentType
> at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417)
> at com.foo.MyServiceStub.fromOM(KnowledgeBaseServiceStub.java:5805)
> When switching the server to use MTOM (only possible for testing), the issue disappear.
> Here is the discussion on axis-user: http://marc.info/?t=119142622400004&r=1&w=4
> Please see attached wsdl, request and response.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org