Yes, this is very much needed feature and is one of the reasons for
entertaining the horrible idea of writing custom xml binding stack.
Specifically I want to tell schema->java compiler when to stop creating
new classes and instead use classes that were created earlier.
Intuitively I want to specify compile/reuse mode based on XSD file name.
But the schema infoset specification doesn't retain import location in
the component definition. Probably that's because import might change
component definitions, either through redefine, chameleon trick, or by
resolving other (shared) schemas differently.
So in general this feature will not work for all possible kinds of
schemas but so what? Let's not make life of developer majority harder...
Thanks,
Gia
> -----Original Message-----
> From: Kohsuke Kawaguchi [mailto:Kohsuke.Kawaguchi_at_Sun.COM]
> Sent: Tuesday, October 28, 2003 7:48 AM
> To: users_at_jaxb.dev.java.net
>
>
> > What solutions are there to this problem?
>
> I'm afraid there's none. I personally think I've been hearing
> this request for a number of times, so hopefully the spec
> people would pick this one up.
>
> The difficulty in doing this is that as far as the W3C XML
> Schema spec is concerned, it is impossible to distinguish
> things defined in mainSchema1.xsd from those defined in
> common.xsd. So the spec cannot describe such a behavior in a nice way.
>
> RELAX NG support of XJC does support this package separation,
> if you are interested.
>
>
> regards,
> --
> Kohsuke Kawaguchi
> Sun Microsystems kohsuke.kawaguchi_at_sun.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jaxb.dev.java.net
> For additional commands, e-mail: users-help_at_jaxb.dev.java.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jaxb.dev.java.net
For additional commands, e-mail: users-help_at_jaxb.dev.java.net