Arnaud Blandin wrote:
> Hi Norval,
>
> > 1. the ability for the SourceGenerator to output a mapping file as
> > well
> > as/instead of
> > the descriptors (if I'm correct and when a mapping file is
> used it
> > has to be complete,
> > then this makes a much more friendlier starting point for
> > overriding a few of the
> > classes)
>
> Why not using the mapping tool that will provide you a mapping file for
> java beans. I am not sure it is a good idea to generate the mapping via
> the source generator. Besides if you don't want the descriptors you can
> turn off the generation by using the -nodesc command line option or via
> the API but be aware that you lose all validation information.
Hi Arnaud,
My interest here was to get as far as possible using the already existing
schema:
- schema => .java files + mapping file for them
- change mapping file to override some classes and add application logic
- write override classes
=> job done
I think Patrick's suggestion about using the <annotation><appinfo> notation
sounds like a great solution.
>
>
> > 2. The SourceGenerator would use naming conventions in generated
> Java
> > files to avoid
> > name collisions (to generate source from my schema I've had to
> > artificially add
> > prefixes to each element name to avoid clashes, e.g. the
> element
> > "Type" gets reused
> > in five different contexts, so I've had to make a CV_Type
> > "Constant
> > Value Type"
> > etc.
>
> This will be solved with the introduction of the Source Generator
> Binding file (hopefully soon).
>
> > *A big pat on the back to the Castor crew!*
>
> Thanks,
>
> Arnaud
You the man! (not to mention the other Castor contributors...)
>
>
> -----------------------------------------------------------
> 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
