| Problems with deriving types [message #597233] |
Tue, 29 November 2005 17:43 |
 Klaas Dellschaft
Messages: 58
Registered: July 2009 |
Member |
|
|
Hi,
I have a problem with extending a complexType with an attribute group.
The following types are defined:
<xs:complexType name="A">
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element name="source" type="element1"/>
<xs:element name="value" type="element2"/>
<xs:group ref="ns:group"/>
</xs:choice>
<xs:attributeGroup ref="ns:attributeGroup1"/>
</xs:complexType>
<xs:complexType name="B">
<xs:complexContent>
<xs:extension base="A">
<xs:attributeGroup ref="ns:attributeGroup2"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
This is part of a very large schema. When validating this schema, I get
the following error message for the type B: "The basetype has
'elementOnly' content so this extended type must also".
And indeed, when I look at the contentTypeCategory of B, it has "emtpy"
while A has a contentTypeCategory of "elementOnly". Until now I failed
to reduce the large schema to a minimal schema reproducing the problem.
Because when I reduce it only to those definition (including the
referenced definitions), the contentTypeCategory of B is also
"elementOnly", so that the error doesn't occur. Probably you have any
idea, why the contentTypeCategory of B may become "empty" sometimes?
I got the problem using XSD 2.1. Until now I had no time to test it with
more recent versions of XSD.
Cheers
Klaas
|
|
|
Powered by
FUDForum. Page generated in 0.01760 seconds
] 
Search
Help
Register
Login
Home
