axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amila Chinthaka Suriarachchi (JIRA)" <>
Subject [jira] Commented: (AXIS2-3259) ADBException: Unexpected subelement contentType
Date Fri, 12 Oct 2007 06:59:51 GMT


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:
>             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(
>        at
> When switching the server to use MTOM (only possible for testing), the issue disappear.
> Here is the discussion on axis-user:
> 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:
For additional commands, e-mail:

View raw message