James,
Also strugling with the setWrapCollectionsInElement().
It is never used btw, so I explain here what I think was intended, can
you please confirm that, since I am making it work that way ;)
First the use case if it is set to true :
<mainelement>
<elements>
<element/>
<element/>
</elements>
</mainelement>
methods : addElement(Element element) and List getElements()
now if it is set to false (the thing I need)
<mainelement>
<element/>
<element/>
</mainelement>
methods : addElement(Element element) and List getElements()
The second sample isn't working correctly.
Is the second case intended to be working like that when it is set to
false?
I am assuming that at the moment, so I can actually parse the damned xml
thing ;), but it would be nice if it is usable..
I will set the default to true, since that is the current behaviour and
we need backwards compaitibility ;).
Mvgr,
Martin
On Wed, 2002-06-05 at 18:42, James Strachan wrote:
> From: "Martin van den Bemt" <[EMAIL PROTECTED]>
> > i'll deprecate the current setNameMapper then and point it to
> > setElementNameMapper, so we keep backwardcompatible ;)
>
> +1.
>
> James
>
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
