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 "Etienne (JIRA)" <ji...@apache.org> on 2007/10/09 14:54:50 UTC
[jira] Created: (AXIS2-3259) ADBException: Unexpected subelement
contentType
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
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
[jira] Updated: (AXIS2-3259) ADBException: Unexpected subelement
contentType
Posted by "Etienne (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Etienne updated AXIS2-3259:
---------------------------
Attachment: request.xml
request
> 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
> Attachments: KnowledgeBaseService.wsdl, request.xml
>
>
> 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
[jira] Commented: (AXIS2-3259) ADBException: Unexpected subelement
contentType
Posted by "Etienne (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533690 ]
Etienne commented on AXIS2-3259:
--------------------------------
Ok, I see my error... i did let the soap envelope in the test file which is wrong.
So, i'm not able to reproduce the issue with your test program.
Here is the full exception from my application:
org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException: Unexpected subelement contentType
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417)
at com.instranet.services.knowledgebase.KnowledgeBaseServiceStub.fromOM(KnowledgeBaseServiceStub.java:5805)
at com.instranet.services.knowledgebase.KnowledgeBaseServiceStub.viewBinaryFiles(KnowledgeBaseServiceStub.java:1462)
at com.instranet.services.clientlib.axis2_13.kb.Axis2KBService.viewBinaryFile(Axis2KBService.java:457)
at com.instranet.services.clientlib.axis2_13.Axis2Wrapper.viewBinaryFile(Axis2Wrapper.java:93)
at com.instranet.services.clientlib.InstraClientLib.viewBinaryFile(InstraClientLib.java:212)
at org.apache.jsp.binaryfilerenderer_jsp._jspService(binaryfilerenderer_jsp.java:77)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:393)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:390)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:263)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:584)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:675)
Caused by: java.lang.Exception: org.apache.axis2.databinding.ADBException: Unexpected subelement contentType
at com.instranet.services.knowledgebase.ArrayOfBinaryFile$Factory.parse(ArrayOfBinaryFile.java:567)
at com.instranet.services.knowledgebase.ViewBinaryFilesResponse$Factory.parse(ViewBinaryFilesResponse.java:405)
at com.instranet.services.knowledgebase.KnowledgeBaseServiceStub.fromOM(KnowledgeBaseServiceStub.java:5752)
... 26 more
Caused by: org.apache.axis2.databinding.ADBException: Unexpected subelement contentType
at com.instranet.services.knowledgebase.ArrayOfBinaryFile$Factory.parse(ArrayOfBinaryFile.java:563)
... 28 more
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:541)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:417)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:390)
The fact is that with two responses that differs only in the values, not in the xml structure, one is succesfuly parsed and the other one not (the latest attached).
I'm attaching the capture of TCP seesion (with CommView), the first one that is OK, the second that leads to the exception above.
> 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
> Attachments: knowledgebase.tar, KnowledgeBaseService.wsdl, request.xml, response.xml, soapbody.xml
>
>
> 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
[jira] Commented: (AXIS2-3259) ADBException: Unexpected subelement
contentType
Posted by "Srinivasan Sairam (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566469#action_12566469 ]
Srinivasan Sairam commented on AXIS2-3259:
------------------------------------------
I am still getting the exception, even though I am using the correct JDK (1.5) and the wstx-asl-3.2.1.jar while invoking the client.
It receives the response from the operation, then it is throwing the exception
org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException: Unexpected subelement errorText
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417)
My wsdl has the following complex type defined as part of the response
<xs:complexType name="RequestStatus">
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" name="errorCodes" nillable="true" type="xs:int"/>
<xs:element maxOccurs="unbounded" minOccurs="0" name="errorText" nillable="true" type="xs:string"/>
<xs:element minOccurs="0" name="overallStatusCode" type="xs:int"/>
<xs:element minOccurs="0" name="overallStatusText" nillable="true" type="xs:string"/>
<xs:element minOccurs="0" name="VALUE_MISMATCH" type="xs:int"/>
<xs:element minOccurs="0" name="VALUE_NOT_FOUND" type="xs:int"/>
<xs:element minOccurs="0" name="STATUS_FAILURE_STRING" nillable="true" type="xs:string"/>
<xs:element minOccurs="0" name="STATUS_SUCCESS_STRING" nillable="true" type="xs:string"/>
</xs:sequence>
</xs:complexType>
Is this a known (and reopened) issue or am I doing something wrong ?
> 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
[jira] Updated: (AXIS2-3259) ADBException: Unexpected subelement
contentType
Posted by "Etienne (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Etienne updated AXIS2-3259:
---------------------------
Attachment: tcp-session-parsing-KO.txt
> 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
> 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
[jira] Commented: (AXIS2-3259) ADBException: Unexpected subelement
contentType
Posted by "Etienne (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533705 ]
Etienne commented on AXIS2-3259:
--------------------------------
OK, I did found the issue...
My client application was missing wstx-asl-3.2.1.jar.
So, some questions:
* why don't i have a class not found exception?
* how can this be an issue for some responses and not for other (again, the only difference is the values within tags, the strcture being the same)?
On the last point, can this depends on the size of the base64binary element? The one that is correctly retrieved is 4.2kb when the one for which there is a failure is 17kb.
> 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
> 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
[jira] Updated: (AXIS2-3259) ADBException: Unexpected subelement
contentType
Posted by "Etienne (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Etienne updated AXIS2-3259:
---------------------------
Attachment: KnowledgeBaseService.wsdl
WSDL
> 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
> Attachments: KnowledgeBaseService.wsdl
>
>
> 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
[jira] Updated: (AXIS2-3259) ADBException: Unexpected subelement
contentType
Posted by "Etienne (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Etienne updated AXIS2-3259:
---------------------------
Attachment: tcp-session-parsing-OK.txt
> 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
> 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
[jira] Commented: (AXIS2-3259) ADBException: Unexpected subelement
contentType
Posted by "Etienne (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533641 ]
Etienne commented on AXIS2-3259:
--------------------------------
I found why you doid not reproduce the issue...
The issue do not occurs on every single response, and the one I attached proviously did not cause the issue.
Reattaching one tha cause the issue:
[java] java.lang.Exception: org.apache.axis2.databinding.ADBException: Unexpected subelement Body
[java] at com.instranet.services.knowledgebase.ViewBinaryFilesResponse$Factory.parse(ViewBinaryFilesResponse.java:427)
[java] at com.instranet.services.RunViewBinaryfilesResponse.main(RunViewBinaryfilesResponse.java:41)
[java] Caused by: org.apache.axis2.databinding.ADBException: Unexpected subelement Body
[java] at com.instranet.services.knowledgebase.ViewBinaryFilesResponse$Factory.parse(ViewBinaryFilesResponse.java:414)
[java] ... 1 more
> 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
> Attachments: knowledgebase.tar, KnowledgeBaseService.wsdl, request.xml, response.xml, soapbody.xml
>
>
> 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
[jira] Updated: (AXIS2-3259) ADBException: Unexpected subelement
contentType
Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amila Chinthaka Suriarachchi updated AXIS2-3259:
------------------------------------------------
Attachment: knowledgebase.tar
can you please test with the generated client and send the whole stack trace.
Can you send the exact line this exception thrown in the code I have sent to you.
I can not reproduce your problem here.
> 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
> Attachments: knowledgebase.tar, KnowledgeBaseService.wsdl, request.xml, response.xml
>
>
> 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
[jira] Issue Comment Edited: (AXIS2-3259) ADBException: Unexpected
subelement contentType
Posted by "Parikshat Sharma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803041#action_12803041 ]
Parikshat Sharma edited comment on AXIS2-3259 at 1/20/10 11:08 PM:
-------------------------------------------------------------------
Hi,
I am facing the same issue as explained in this JIRA.
I am using Axis 2.1.4 to generate the Client Code for a web service exposed by the Vendor server. In the resolution for this case I find that the cause was identified as usage of incorrect Jars. Could you inform me which Jars were incorrect?
Error received -
org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException: Unexpected subelement Parameter.
Here Parameter is always one of the referenced parameters in the XSD. This issue is occurring in all the cases which have a referenced Parameter.
Regards,
Parikshat Sharma
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp
was (Author: pasharma@amdocs.com):
Hi,
I am facing the same issue as explained in this JIRA.
I am using Axis 2.1.4 to generate the Client Code for a web service exposed by the Vendor server. In the resolution for this case I find that the cause was identified as usage of incorrect Jars. Could you inform me which Jars were incorrect?
Error received -
org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException: Unexpected subelement Parameter.
Here Parameter is always one of the referenced parameters in the XSD. This issue is occurring in all the cases which have a referenced Parameter.
Regards,
Parikshat Sharma
SSME
Amdocs Activation Manager
+357-25-88-6306 (Desk)
+357-99-01-7515 (Mobile)
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp
> ADBException: Unexpected subelement contentType
> -----------------------------------------------
>
> Key: AXIS2-3259
> URL: https://issues.apache.org/jira/browse/AXIS2-3259
> Project: 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.
[jira] Updated: (AXIS2-3259) ADBException: Unexpected subelement
contentType
Posted by "Etienne (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Etienne updated AXIS2-3259:
---------------------------
Attachment: response.xml
response
> 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
> Attachments: KnowledgeBaseService.wsdl, request.xml, response.xml
>
>
> 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
[jira] Assigned: (AXIS2-3259) ADBException: Unexpected subelement
contentType
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deepal Jayasinghe reassigned AXIS2-3259:
----------------------------------------
Assignee: Amila Chinthaka Suriarachchi
> 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
[jira] Commented: (AXIS2-3259) ADBException: Unexpected subelement
contentType
Posted by "Parikshat Sharma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803041#action_12803041 ]
Parikshat Sharma commented on AXIS2-3259:
-----------------------------------------
Hi,
I am facing the same issue as explained in this JIRA.
I am using Axis 2.1.4 to generate the Client Code for a web service exposed by the Vendor server. In the resolution for this case I find that the cause was identified as usage of incorrect Jars. Could you inform me which Jars were incorrect?
Error received -
org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException: Unexpected subelement Parameter.
Here Parameter is always one of the referenced parameters in the XSD. This issue is occurring in all the cases which have a referenced Parameter.
Regards,
Parikshat Sharma
SSME
Amdocs Activation Manager
+357-25-88-6306 (Desk)
+357-99-01-7515 (Mobile)
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp
> ADBException: Unexpected subelement contentType
> -----------------------------------------------
>
> Key: AXIS2-3259
> URL: https://issues.apache.org/jira/browse/AXIS2-3259
> Project: 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.
[jira] Commented: (AXIS2-3259) ADBException: Unexpected subelement
contentType
Posted by "Etienne (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534237 ]
Etienne commented on AXIS2-3259:
--------------------------------
Got it.
I am compiling my client with jdk 1.5 but running it with jdk 1.6.
As for now MTOM cannot be enabled as we do have various non-MTOM enabled clients using the service.
Is there some documentation on which jars are required for a client?
Thanks for your help
Etienne
> 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
> 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
[jira] Commented: (AXIS2-3259) ADBException: Unexpected subelement
contentType
Posted by "Liron Raveh (JIRA)" <ji...@apache.org>.
[ 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
[jira] Resolved: (AXIS2-3259) ADBException: Unexpected subelement
contentType
Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amila Chinthaka Suriarachchi resolved AXIS2-3259.
-------------------------------------------------
Resolution: Cannot Reproduce
this bug is due to usage of wrong jars.
> 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
[jira] Commented: (AXIS2-3259) ADBException: Unexpected subelement
contentType
Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533674 ]
Amila Chinthaka Suriarachchi commented on AXIS2-3259:
-----------------------------------------------------
this should not be the problem. it says Unexpected subelement Body this means you have put the
soap envelop and body elements to that.
if you want to parse directly with the ADB class you have to remove this.
> 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
> Attachments: knowledgebase.tar, KnowledgeBaseService.wsdl, request.xml, response.xml, soapbody.xml
>
>
> 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
[jira] Updated: (AXIS2-3259) ADBException: Unexpected subelement
contentType
Posted by "Etienne (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Etienne updated AXIS2-3259:
---------------------------
Attachment: soapbody.xml
> 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
> Attachments: knowledgebase.tar, KnowledgeBaseService.wsdl, request.xml, response.xml, soapbody.xml
>
>
> 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
[jira] Commented: (AXIS2-3259) ADBException: Unexpected subelement
contentType
Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534233 ]
Amila Chinthaka Suriarachchi commented on AXIS2-3259:
-----------------------------------------------------
if you have not used the wstx-asl-3.2.1.jar then from where it has got the stax implementaion. Are you working with the jdk 1.6?
Handling binary data is done through OM and there may be problems with the other stax implentations. (we have test with wstx-asl).
For the second question there are limitaions for sending binary data directly as base64Encodings . So please enable MTOM and use it for larger files. with MTOM you can even send 1GB files as well.
> 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
> 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