Using latest 1.1.1 snapshot, with JDK 1.4.2.

I don't know what about this is particular to the problem, but I have a
schema with some structures that look like this:

-----------------
        <xs:complexType name="UpdateCommentSetType">
                <xs:sequence>
                        <xs:element name="ActionCode"
type="ActionCodeType"/>
                        <xs:element name="CommentSet"
type="CommentSetType" maxOccurs="unbounded"/>
                </xs:sequence>
        </xs:complexType>
        <xs:complexType name="CommentSetType">
                <xs:sequence>
                        <xs:element name="QuestionnaireInstanceId"
type="String40Type" minOccurs="0"/>
                        <xs:element name="QuestionId"
type="String40Type" minOccurs="0"/>
                        <xs:element name="Comment" type="CommentType"
minOccurs="0" maxOccurs="unbounded"/>
                        <xs:element name="CommentSet"
type="CommentSetType" minOccurs="0" maxOccurs="unbounded"/>
                </xs:sequence>
        </xs:complexType>
-----------------

Note that CommentSetType includes element "CommentSet", of type
"CommentSetType" (with minOccurs="0").

If I generate the code for this with 'warnings="false"', it appears to
complete (and compiles), although it says this during code generation:

INFO: Resolving conflict for local element
/complexType:CommentSetType/CommentSet[/complexType:CommentSetType]
against another local element of the same name.

If I instead set 'warnings="true"', it fails with a StackOverflowError,
printing the following message until it dies:

WARNING: Warning: A class name generation conflict has occured between
element
'/complexType:CommentSetType/CommentSet[/complexType:CommentSetType]'
and element
'/complexType:UpdateCommentSetType/CommentSet[/complexType:CommentSetTyp
e]'. Please use a Binding file to solve this problem.

I prefer to have it print warnings, if possible.

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply via email to