Problem JAXB Unmarshaller if order of XML tags differs.

[Yogesh Gandhi]

Hello friends,

I am a bit new to XSD and XML unmarshalling techniques. In past month I have learnt JAXB techniques of how to unmarshal an given XML into a JAVA object.

I am using Java web services developer pack for that purpose.

Can someone tell if the order of tags matter while umarshalling an XML?

I have an XML of type
<parent> <child1>Apple</child1> <child2>Orange</child2> </parent>

I created an XSD of kind..

<xsd:element name="parent"> <xsd:complexType> <xsd:sequence> <xsd:element name="child1" type="xsd:string" /> <xsd:element name="child2" type="xsd:string" /> </xsd:sequence> </xsd:complexType> </xsd:element>

I generated the java files using JWSDP. and written the code for unmarshalling.

It works if child 1 comes before child2. In case child2 comes before child1, then it gives me an unmarshalling exception as follows

javax.xml.bind.UnmarshalException: Unexpected element {}:child2
	at javax.xml.bind.UnmarshalException.<init>(UnmarshalException.java:72)
	at 

Does the order of tags should matter??? How can I get rid of this problem?

Does anyone has any clue?

[Yogesh Gandhi]

I got the solution to my problem :

Someone answered.

This exception has been generated because JAXB follows grammar defined in XSD. In XSD you have used <xsd:sequence> which forces elements to be in-order.

Use <xsd:all> as follows to have un-ordered child. This will solve your problem.

<xsd:all>
<xsd:element name="child1" type="xsd:string" />
<xsd:element name="child2" type="xsd:string" />
</xsd:all>