Hi Werner, yes, I'd like to do so. I'll elaborate the sample domain classes over the weekend. where/how can I turn the how-to document in?
best regards, Georg Georg, > > how about writing up a new HOW-To document that explains the use of the > container attribute based upon your sample domain classes,and hosws what > would be (un)marshalled with and without use of that attribute ? > > Werner > > Werner Guttmann wrote: > > Georg, > > > > the following mapping does the trick (for me). > > > > <mapping> > > <class name="xml.georg2.Data"> > > <map-to xml="data" /> > > <field name="data" type="xml.georg2.A" collection="array"> > > <bind-xml name="a" node="element" /> > > </field> > > </class> > > <class name="xml.georg2.A"> > > <field name="field" type="xml.georg2.B" container="true" > > collection="array"> > > <bind-xml name="value" node="element" /> > > </field> > > <field name="id" type="xml.georg2.C" container="true"> > > <bind-xml name="c" /> > > </field> > > </class> > > <class name="xml.georg2.B"> > > <field name="value" type="integer" /> > > </class> > > <class name="xml.georg2.C"> > > <field name="id" type="java.lang.String"> > > <bind-xml name="id" node="attribute"/> > > </field> > > <field name="name" type="java.lang.String"> > > <bind-xml name="name" node="attribute"/> > > </field> > > </class> > > </mapping> > > > > Regards > > Werner > > > >

