axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Etienne (JIRA)" <>
Subject [jira] Commented: (AXIS2-3259) ADBException: Unexpected subelement contentType
Date Wed, 10 Oct 2007 11:19:50 GMT


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:
>             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