> 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.
Thanks for all the input. Things are becoming clearer but I still don't
fully understand the argument. You seem to be implying that it is the
fault of the XML Schema specification as to why the Java packaging model
I require is not possible. Could you give me an example (in simple
terms) as why this is the case? I still don't see why the Schema
specification influences the Java packaging model (surely they should be
de-coupled).
I must admit I have only read snippets of the XML Schema specification
so apologies if this scenario is obvious to most people.
Adrian
-----Original Message-----
From: Kohsuke Kawaguchi [mailto:Kohsuke.Kawaguchi_at_Sun.COM]
Sent: 28 October 2003 15:48
To: users_at_jaxb.dev.java.net
Subject: Re: Java packages with relation to Nested schemas.
> 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