[
https://issues.apache.org/jira/browse/AXIS2-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803041#action_12803041
]
Parikshat Sharma commented on AXIS2-3259:
-----------------------------------------
Hi,
I am facing the same issue as explained in this JIRA.
I am using Axis 2.1.4 to generate the Client Code for a web service exposed by
the Vendor server. In the resolution for this case I find that the cause was
identified as usage of incorrect Jars. Could you inform me which Jars were
incorrect?
Error received -
org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException:
Unexpected subelement Parameter.
Here Parameter is always one of the referenced parameters in the XSD. This
issue is occurring in all the cases which have a referenced Parameter.
Regards,
Parikshat Sharma
SSME
Amdocs Activation Manager
+357-25-88-6306 (Desk)
+357-99-01-7515 (Mobile)
This message and the information contained herein is proprietary and
confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp
> 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.
