This one time, at band camp, Norm Deane said:
ND>> > 2) We need flexibility to define our object model
ND>> independent of the
ND>> > XML document format. It looks like Castor maps a class
ND>> directly to an
ND>> > element. For us this is not acceptable.
ND>>
ND>> Castor can certainly handle this via the mapping descriptor.
ND>> The mapping
ND>> descriptor is an XML file that describes how objects are
ND>> mapped to one
ND>> another as well as how objects should be marshalled and unmarshalled.
ND>>
ND>
ND>How flexible is it? We don't want to have to map our object model directly
ND>to the cXML DTD. There are some elements in the document we don't care
ND>about. We also don't want to have to map each element in the document to an
ND>object in our object model. We may roll multiple elements into a single
ND>object in some cases and other times want to split an element into multiple
ND>objects.
The Source Generator provides a lot of flexibility. More info can
be found here:
http://www.castor.org/sourcegen.html
AFAIK, there is no manner in which to tell the Source Generator to
ignore certain elements or types in an XSD.
But remember that there is no requirement to use the Source Generator.
You can map to existing objects for marshalling/unmarshalling just
fine.
Bruce
--
perl -e 'print unpack("u30","<0G)[EMAIL PROTECTED]&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'
The Castor Project
http://www.castor.org/
Apache Geronimo
http://incubator.apache.org/projects/geronimo.html
