Sven
what classes are being generated in your case ? And I don't think that
there's actually a naming conflict in your case, as in both cases the
class generatd for the local element definition 'c' would be named
C.java and extend CType1.java.
Werner
[EMAIL PROTECTED] wrote:
Hi!
Can anybody tell me why the automated conflict type resolution does not
work for this example? I'm sure the castorbuilder.properties are used, since
when I'm using "CType2" as type in the "BType" element, resolving works
properly and when I'm disabling the automatic conflict resolution, I'm
getting suitable warning messages.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"; elementFormDefault="qualified"
attributeFormDefault="unqualified">
<xs:complexType name="AType">
<xs:sequence>
<xs:element name="c" type="CType1" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="BType">
<xs:sequence>
<xs:element name="c" type="CType1" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:schema>
The 'XPATH' conflict resolution strategy should solve that problem, shouldn't
it?
Why does it not work?
I'm using Castor and Castor-CodeGen 1.1.2.1.
BTW: What has a valid binding file to look like, in order to solve this issue?
Thanks in advance,
Sven
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
