Thank you very much for the test case, and I'm really sorry for being
unable to catch this bug before we ship it. The problem is confirmed and
fixed in our workspace.
Essentially the problem is having a list directly inside a choice. So
the following re-write avoids the problem.
<xs:group name="Bar">
<xs:choice>
<xs:group ref="Alist" />
<xs:element name="B" type="xs:string"/>
</xs:choice>
</xs:group>
<xs:group name="Alist">
<xs:sequence>
<xs:element name="A" type="xs:string" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
Hope this is OK with you...
regards,
--
Kohsuke KAWAGUCHI 408-276-7063 (x17063)
Sun Microsystems kohsuke.kawaguchi_at_sun.com