[XMLSCHEMA-10] Serialized xs:restriction puts xs:attribute before xs:simpleType when it should not

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: XmlSchema 1.4.4, XmlSchema 1.4.6, XmlSchema 1.4.7
• Fix Version/s: XmlSchema 1.4.7, XmlSchema 2.0.1
• Labels: serialization
• Assignee: Daniel Kulp
• Reporter: William Eliot Kimber
• Created: 29/Mar/11 20:27
• Updated: 15/Sep/11 17:22
• Resolved: 15/Sep/11 15:09

Description

GIven this original markup:

<xs:restriction base="xs:anyType">
<xs:sequence>
<xs:any processContents="lax" minOccurs="0" maxOccurs="0"/>
</xs:sequence>
<xs:attribute name="lang" use="optional"/>
</xs:restriction>

After parsing and serializing the schema with no intervening modification, the serialized result is:

<xs:restriction base="tns:SimpleLiteral">
<xs:attribute name="lang" use="prohibited"/>
<xs:simpleType>
<xs:restriction base="xs:string"/>
</xs:simpleType>
</xs:restriction>

Note the xs:attribute before the xs:simpleType.

The bug appears to a simple coding error in org.apache.ws.commons.schema.XmlSchemaSerializer.serializeSimpleContentRestriction(Document, XmlSchemaSimpleContentRestriction, XmlSchema) in that it's putting the attributes out before the inline simple type.

I can provide a simple unit test that demonstrates the failure if needed.