Hi Stephen,
Stephen Bash wrote:
Keith-
Side note on this issue... I don't recognize the container="true" attribute to the field element. What functionality does it add?
Strange, I could have sworn container was specified on the xml-mapping docs, but it's not there. It's a pretty old attribute, yet-another undocument feature. :-)
Anyway, marking something as a container basically means that it's simply a wrapper and not a first-class object and castor will not produce an xml element for the object. The items inside a container are treated as first-class objects and will have xml elements or attributes associated with them, unless otherwise specified.
By default all collection fields are treated as containers, and all non-collection fields are treated as non-containers.
Cheers,
--Keith
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-user
