> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 16, 2003 10:32 AM
> To: [EMAIL PROTECTED]
> Subject: [castor-dev] Using imports in XML Schema
>
>
> So it looks as if you can only do one name space at a
> time in castor.
This doesn't sound right, but I don't fully understand. I'll read on.
> So when importing from another schema you have to manually
> add the proper
> import statements. This sound right to everyone?
You mean <import> tags, right? If so, yes. This is standard XML Schema -- decent XML
editors or validators understand this arrangement. <xsd:import namespace="
[[logical]] " schemaLocation="[[physical]]"/>
> Is there a way for
> Castor to do the import statements automatically?
Not that I know of. Castor would have to assume that
a namespace is a physical URL, which it is not; it is a URI.
URI's are logical -- they don't necessarily point to a physical resource.
> Will setting org.exolab.castor.builder.nspackages do the right
> thing?
I don't think so.
> Is there a way to specifiy the location of the properties file from the
> command line?
> Seems kind of cumbersome having to pack a jar every time you
> make an edit.
You don't have to pack the jar.
Unzip the properties file into a directory structure that matches that in the jar.
Then put that unfolded structure into the classpath before the castor jar.
>
> - Travell
>
> _____________________________________________________
>
> Travell Perkins
> Senior Associate / Application Developer Consultant
> globallink / State Street Bank
> [EMAIL PROTECTED]
> _____________________________________________________
>
> -----------------------------------------------------------
> 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
