You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by dugolf <ga...@free.fr> on 2011/12/06 10:24:54 UTC
AXIS 1.3 parsing error on optional elements
My soap message contains 1 mandatory element and 3 optionals complexe type
(minOccurs = 0):
<xs:element name="SetEndControlData">
<xs:complexType>
<xs:sequence>
<xs:element name="ControlResult"
type="s0:ControlResultType">
</xs:element>
<xs:element minOccurs="0"
maxOccurs="unbounded" name="DocumentsInformations"
type="s0:DocumentsType">
</xs:element>
<xs:element minOccurs="0"
name="Anomalies" type="s0:AnomaliesType">
</xs:element>
<xs:element minOccurs="0" name="FNT"
type="s0:FNTType"/>
</xs:sequence>
</xs:complexType>
</xs:element>
When the two first optional element are missing, axis try to map the data of
the last optional element with the first element (and then there is a
parsing error)
Where is my mistake (in the xsd, in the parameters of Wsdl2java, in the
configuration of the axis server) ?
--
View this message in context: http://old.nabble.com/AXIS-1.3-parsing-error-on-optional-elements-tp32922992p32922992.html
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org