I think this is coming from the behavior in Xerces. As you might know,
the XML Schema spec is so ambiguous that the schema processors are
allowed to ignore arbitrary <xs:import>s.
I think the way Xerces behaves is that it only honors the first
<xs:import> for every namespace, and it just ignores all the successive
<xs:import>s for that namespace.
You can use the "-nv" switch to bypass the correctness check by Xerces,
if you just want this to compile.
But if you are writing a schema that you expect other people to use,
then you might actually want to redesign your modularization.
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