Hi Bryan,

if you have generated classes with Castor's code generator you will not
need a mapping to marshal/unmarshal them. All the information required
for that is already contained in the discriptor classes generated.

The only reason to require a mapping that i can think of is, that you
like to persist these classes to a databse with Castor JDO.

If that's the case for you, you anyway have to adjust the mapping
generated by hand. Having said that the problems you mentioned are the
result of improvements to the code generator while the mapping tool is
somewhat out of date.

Your offer to contribute to the documentation is very welcome. I suggest
you to review the current docs from your view, the user perspective. As
we may be blind sometimes and do not see the obvious areas where the
current info is misleading or misses anything.

Regards
Ralf

PS: Wouldn't the improvement of mapping tool also be a good idea for a
GSoC project.


Bryan Ward schrieb:
> 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"
> ?  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. 
> 
> 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.
> 
> Cheers,
> 
> Bryan
> 
> 

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to