[
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
