I wrote:
> Also, is the <package> node in any way a replacement for
> the property org.exolab.castor.builder.nspackages?
When you generate code, the answer is yes.
> How about for the SourceGenerator -package command line
> parameter?
Again, when you generate code, the answer is yes, as long as you
put the same targetNamespace in both your schema and the binding file.
I have another question, though. This ns-package mapping would
be very helpful when unmarshalling. Is there any code that inspects
the bindingfile during unmarshalling?
I want it to detect a ns in an instance doc, locate the corresponding
java package in the binding file and then unmarshall the data.
Also, I still haven't answered my original question:
The binding file html doc says the <package> element allows you "to define the mapping
between a schemaLocation attribute and a Java package".
Does this mean that the following binding file will place
all generated objects for Customer.xsd into the 'vo' package?
It's not working for me.
<cbf:binding xmlns:cbf="http://www.castor.org/SourceGenerator/Binding";
defaultBindingType='type'>
<cbf:package>
<cbf:name>vo</cbf:name>
<cbf:schemaLocation>./Customer.xsd</cbf:schemaLocation>
</cbf:package>
</cbf:binding>
Thanks,
Erik
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
