has anyone had difficulties resolving xsd:import ...
schemaLocation="..." under windows?
i have a large schema tree which i use xjc to compile (using the xjc ant
task and a nested <schema> fileset) just fine on unix/osx, but which
borks on windows. i saw a post to this list some time ago suggesting
that you not use schemaLocation="../foo.xsd" but rather
schemaLocation="file://../foo.xsd", so that the jvm will correctly
resolve things (and turn '/' into '\', etc). doing this i get fewer
errors, but still failures (types aren't being resolved or are being
resolved more than once).
any windows users have some suggestions?
failing any clear shortcoming in my use of the above, i might introduce
an intermediate step which creates a master schema with no elements and
nothing but imports, and then point xjc at that single file, instead of
using a nested <schema>. still, if i can make this work without having
to write intermediate code, that'd be awesome.
jon
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jaxb.dev.java.net
For additional commands, e-mail: users-help_at_jaxb.dev.java.net