[jboss-jira] [JBoss JIRA] Closed: (JBXB-90) Wildcard bindings are not detected in complicated/nested model groups

[Adrian Brock (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBXB-90?page=all ]

Adrian Brock closed JBXB-90.
----------------------------

    Resolution: Done

Fixed the TypeBinding.getWildcard() to not end the search at the first nested model group.

> Wildcard bindings are not detected in complicated/nested model groups
> ---------------------------------------------------------------------
>
>                 Key: JBXB-90
>                 URL: http://jira.jboss.com/jira/browse/JBXB-90
>             Project: JBoss XML Binding (JBossXB)
>          Issue Type: Bug
>    Affects Versions: JBossXB-1.0.0.CR7
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For: JBossXB-1.0
>
>
> Nested wilcard bindings are not detected if the model group contains a nested wildcard with
> another nested model group before the wildcard.
> This example shows the problem:
>    <xsd:complexType name="nested-wildcard" mixed="true">
>       <xsd:sequence>
>          <xsd:element name="e1" type="xsd:string"/>
>          <xsd:choice minOccurs="0">
>             <!-- This nested model group "masks" the later wildcard binding -->
>             <xsd:sequence>        
>                <xsd:element name="e2" type="xsd:string" minOccurs="0"/>
>                <xsd:element name="e3" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
>             </xsd:sequence>
>             <xsd:element name="e4" type="xsd:string"/>
>             <xsd:any namespace="##other" processContents="strict"/>
>          </xsd:choice>
>       </xsd:sequence>
>    </xsd:complexType>
> I've created a NestedWilcardUnitTestCase for this.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira