Issue 157 in genxdm: Schema parser mistakenly reports cyclic types error

[gen...@googlecode.com]

Status: New
Owner: joe.bays...@gmail.com
Labels: Type-Defect Priority-Medium Milestone-Release1.1
Component-Processors

New issue 157 by joe.bays...@gmail.com: Schema parser mistakenly reports
cyclic types error
https://code.google.com/p/genxdm/issues/detail?id=157

If TypeB extends TypeA and TypeA's content model has a reference to TypeB,
we're reporting an cyclic type error. That's incorrect. Here's a schema
to reproduce the issue:

<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://test" xmlns="http://test"
elementFormDefault="qualified" attributeFormDefault="unqualified">
<xsd:complexType name="AType" abstract="true">
<xsd:sequence>
<xsd:element name="bElem" type="BType" minOccurs="0"
maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="BType">
<xsd:complexContent>
<xsd:extension base="AType">
<xsd:sequence>
<xsd:element name="foo" type="xsd:string" minOccurs="0"
maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:schema>


--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[gen...@googlecode.com]

Updates:
Status: Fixed

Comment #1 on issue 157 by joe.bays...@gmail.com: Schema parser mistakenly

reports cyclic types error
https://code.google.com/p/genxdm/issues/detail?id=157

Fixed at revision 521. Now, when converting interim XMLType objects to
model Type, we add the newly minted ComplexTypeImpl to the outBag before
processing its baseType.