Castor doesn't generate source for imports automatically, you can enable that by
adding the command line flag:
-generateImportedSchemas
actually now that I type that it seems a bit long to me, I'll see if I can shorted
than up, like -generateImports instead.
--Keith
[EMAIL PROTECTED] wrote:
> I recently moved part of my schema into a second file because it contained types
> that another group uses. My main schema imports the other group's schema as well as
> the W3C xlink schema. It worked fine with just xlink but when I created the
> othergroup.xsd, I ran into compile errors: One of the classes in the main schema
> (and main package) refers to a class in the othergroup schema (in a different
> package). SourceGenerator fails to generate an import statement for the imported
> class nor does it fully qualify the classname with the other package.
>
> Here is how I generate the source:
>
> java org.exolab.castor.builder.SourceGenerator -i mainschema.xsd -types j2 -package
> org.myorg.myproject -dest .
> java org.exolab.castor.builder.SourceGenerator -i othergroup.xsd -types j2 -package
> org.myorg.otherproject -dest .
> java org.exolab.castor.builder.SourceGenerator -i xlink.xsd -types j2 -dest .
>
> Is this a bug in the SourceGenerator (possibly bug #1144) or is it how I am
> generating the source??
>
> Thanks...
> Robert
>
> -----------------------------------------------------------
> 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
