[
https://issues.apache.org/jira/browse/AXIS2-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922896#action_12922896
]
chenfeng commented on AXIS2-3259:
---------------------------------
hi.
I have same issue with it.
> <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>
[wsdl2java.bat -uri file:///C:\axis2-1.4.1\bin\test.wsdl -p org.test.test1-o
test -d adb -s -wv 1.4.1 -ss -sd]
the source create by this parameter , the source of base64Binary should be a
bug in it.
if I add a line in method [parse] in BinaryFile.java
[reader.next();]
after
[ if (isReaderMTOMAware(reader)
&&
java.lang.Boolean.TRUE.equals(reader.getProperty(org.apache.axiom.om.OMConstants.IS_BINARY)))
{
//MTOM aware reader - get the
datahandler directly and put it in the object
object.setContent(
(javax.activation.DataHandler)
reader.getProperty(org.apache.axiom.om.OMConstants.DATA_HANDLER));
]
the Exception about ADBException will be disappear.
The reason seem that when reader.xml move beween xml file it have a more next
move in base64Binary type.
I wish this infomation will help you all.
Regards,
chenfeng
> 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
