i see. so both the container attribute and the element
exist explicitly to support situations where an object
model and an xml schema don't have direct one to one
correspondence. the xml may have additional intermediate
container tags (with no correspondence on the java side)
and vice versa ('intermediate' java objects may have no
corresponding tags).
thank you for taking the time to explain this.
/ eitan
-----Original Message-----
From: Keith Visco [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 26, 2002 12:43 AM
To: [EMAIL PROTECTED]
Subject: Re: [castor-dev] help understanding "container" concept in
mapping
Hi Eitan,
I don't think it's used any more. Perhaps the JDO team uses it, but it's
not used on the XML side.
For Castor XML, we currently support container objects. A container
object is an object that does appears in the Java object model, but does
not have a direct representation in the XML, yet it's children do.
An example of a container might be a collection, such as a Vector or
Array, where only the items in the collection should be marshalled.
Simply use <field ... container="true"> to indicate the field is a
container.
We plan on supporting container elements also, but we do not yet have
anyone working on it.
Container elements are elements that appear in the XML, but that do not
have a direct object representation, while it's children map to fields
in the parent of the container element.
Thanks,
--Keith
Eitan Suez wrote:
>
> hi,
>
> i am trying to understand the concept of the
> <container> element & accompanying attribute in a
> mapping file.
>
> can someone who does understand this and who does
> have a little spare time provide an explanation?
>
> from the mapping schema, i infer that a field can
> be marked with container="true|false"
>
> q1: what is the significance of this 'marker'?
>
> also, a class element can have an optional reference
> to a container. the definition of the container
> element is very similar to that of a field, with
> attributes such as name, type, required, direct,
> get-method, etc..
>
> so i assume that a class can be contained by another
> class and information about the containing class
> and how to access it from the "contained" class can
> be described in the mapping.
>
> what i lack in understanding this mechanism is the
> underlying purpose and utility.
>
> an example would probably clarify things for me.
>
> thank you in advance.
>
> / eitan
>
> -----------------------------------------------------------
> 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
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
