Hi Mike,
This can be done. And yes it does matter if you use include instead of
import because include acts as a "inlining" and treats everying in the
included schema as if it was part of the including schema. <import> is
what you want to use. Schema B and C will need it's own targetNamespace
and you'll need to set up your namespace to package mappings in the
castorbuilder.properties file so that Castor knows how to generate the
correct code.
--Keith
Mike Kopack wrote:
Hey gang,
I'm new to Castor and I'm having a hard time getting it to generate the
classes the way that I need them to. What I have is the following:
Schema A - defines a set of complexTypes, simpleTypes and some shared
Elements.
Schemas B and C - different schemas that make use of the types and
elements defined in A, through either an import or include.
What I NEED to have Castor do is generate 3 packages:
package A - containing the code/classes for everything in A.
package B - containing the code/classes for B, with references as needed
to the classes in package A (ie, not make it's own local package copy of
things defined in A)
package C - containing the code/classes for C, with references as needed
to the classes in package A (ie, not make it's own local package copy of
things defined in A)
When I try to do this, Castor always spits out package A, then packages
B and C with all the same elements as A in their own package (plus their
B and C specific classes).
Is there any way to fix that???
Also, does it matter if I do an Import rather than an Include?
Thanks!
--Mike
-------------------------------------------------
If you wish to unsubscribe from this list, please send an empty message
to the following address:
[EMAIL PROTECTED]
-------------------------------------------------
-------------------------------------------------
If you wish to unsubscribe from this list, please
send an empty message to the following address:
[EMAIL PROTECTED]
-------------------------------------------------
