Franklin,
This issue is already on our to-do list. And we are interested in
solving it. If you have some time and would like to take a shot at
providing a patch, feel free to do so. Otherwise, you'll have to wait
until myself, or someone else, has a chance to get to it.
Thanks,
--Keith
[EMAIL PROTECTED] wrote:
>
> I am having a serious problem with SourceGenerator operating on an XML
> Schema: we have a large schema that has constructs that cause
> trouble, i.e.,
>
> <xs:element name="foo" type="foo">
> ...
> </xs:element>
>
> runs into the recently discussed problem of AGSet.java being generated
> both for the element and the type if "element" is chosen for the
> property
> org.exolab.castor.builder.javaclassmapping
>
> But also, there is the problem of overloading multiple but different
> element and type and attribute names:
>
> <xs:element name="foo">
> <xs:attribute name="x">
> ...
> </xs:attribute>
> </xs:element>
> ...
> <xs:element name="bar">
> <xs:attribute name="x">
> ...
> </xs:attribute>
> </xs:element>
>
> It seems critical that Castor be able to automatically respect the
> nested scopes of everything, and therefore generate Java classes of
> different names, e.g., by either using a number or a meaningful
> qualifier:
>
> XType.java
> XType1.java
> XType2.java
> ...
>
> XTypeFoo.java
> XTypeBar.java
> XTypeBaz.java
> ...
>
> Ideally, of course, there should be a way for the user to specify the
> mapping, but for our purposes it would suffice simply to avoid
> collisions, because it does not seem reasonable to ask every schema
> writer to make every single name unique.
>
> --
> Franklin
>
> -----------------------------------------------------------
> If you wish to unsubscribe from this mailing, send mail to
> [EMAIL PROTECTED] with a subject of:
> unsubscribe castor-dev
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
