The second schema (...resource.lists.xsd) is a modified copy of the one
that's pulled in by
<xs:import namespace="urn:ietf:params:xml:ns:resource-lists"
schemaLocation="urn.ietf.params.xml.ns.resource.lists.xsd" />
in the other one.
Using the original one doesn't compile either; the schema compiler complains
about
<xs:complexType name="listType">
<xs:sequence>
<xs:element name="display-name" type="display-nameType"
minOccurs="0" />
<xs:sequence minOccurs="0" maxOccurs="unbounded">
<xs:choice>
<xs:element name="list">
<xs:complexType>
<xs:complexContent>
<xs:extension base="listType" />
</xs:complexContent>
</xs:complexType>
</xs:element>
...
</xs:choice>
</xs:sequence>
...
</xs:sequence>
...
</xs:complexType>
I can't tell whether this is justified. Just using
<xs:element name="listt" type="listType" />
works, though.
-W
On Wed, Dec 23, 2009 at 10:25 AM, Lulseged Zerfu <
lulseged.zerfu_at_ericsson.com> wrote:
> Hi
>
> I have two schemas that I need to compile and I get a conflict. This is a
> problem in the second schema. They should not have used the list-type when
> it was already used in the ietf schema.
>
> But is there anyway that jaxb can solve this problem? Can it be
> customized?
>
> <<urn.ietf.params.xml.ns.resource.lists.xsd>> <<urn.oma.xml.poc.list.service.xsd>>
>
>
> Lulseged
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jaxb.dev.java.net
> For additional commands, e-mail: users-help_at_jaxb.dev.java.net
>