Bryan,
just adding to what Ralf already said. And my first question would have
been 100% identical to Ralf's: why generate a mapping file when you
generated descriptor classes anyhow during code generation .. ;-).
Werner
Bryan Ward wrote:
Hi Werner,
I was using the MappingTool to generate a mapping file from a class that
had been code-gen'd from a schema and noticed some interesting facets
within the mapping file. First of all for a list / collection it
normally defaults the collection attribute to "array". In looking at
the generated code the field is actually an ArrayList so according to
the xml mapping documentation, shouldn't that attribute read "arraylist"
?
Yes, it should. I'd consider this a source for a bug report/enhancement
request.
Secondly on a different occasion, the generated mapping file listed
"enumerate" for the collection attribute of the field. Again looking at
the xml mapping documentation I can find no reference to "enumerate" as
being a valid collection type.
It actually isn't. But there's support for enumerate*() methods as
getetr method when declaring a field mapping. Again, I'd be interested
to see a sample XML schema (fragment) from which I can generate classes
and a mapping file and abserve that behaviour.
So is enumerate a valid collection type? How about array vs arraylist?
And for the record let me just state how much I (and the rest of the
castor using world) appreciate the work that you all put into castor
even with your day jobs etc and if there are opportunities for us castor
users to "give back" i.e. update documentation, author / amend "how tos"
please let us know.
Thank you so much for the positive feedback. It really makes a
difference. Having said that, Castor is open source. As such, it relies
on its user community, incl. contributions fro documentation, HOW-TOs,
code, etc. In other words, feel free to throw anything at us, and we'll
find the time to get it integrated. It's only through this that we can
improve the overall experience.
Cheers,
Bryan
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
