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 "Stefano Ghezzi (JIRA)" <ji...@apache.org> on 2019/01/02 11:05:00 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=16731944#comment-16731944 ] 

Stefano Ghezzi commented on AXIS2-3259:
---------------------------------------

I had the same problem. When the base64binary overcame 16k limit the parse start giving the error, Substantially it stops reading the content after 16k so obviously the rest of the document seems corrupted.

My problem was that i was using com.sun.xml.stream.XMLReaderImpl. 

Removing

<dependency>
 <groupId>com.sun.xml.stream</groupId>
 <artifactId>sjsxp</artifactId>
</dependency>

and adding

<dependency>
 <groupId>org.codehaus.woodstox</groupId>
 <artifactId>wstx-asl</artifactId>
</dependency>

solved my problem (so wstx as suggested before was working)

> 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
>            Priority: Major
>         Attachments: KnowledgeBaseService.wsdl, knowledgebase.tar, 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 was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org