axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dugolf <gauthier.mic...@free.fr>
Subject Axis 1.3 parsing error on optional elements
Date Tue, 06 Dec 2011 09:18:02 GMT

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-tp32922966p32922966.html
Sent from the Axis - Dev mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


Mime
View raw message