On Mon, 05 Dec 2005 02:19:55 -0500, Andrus Adamchik
<andru..bjectstyle.org> wrote:
> See my reply to Cris. It is not only redundant, but also presents a
> problem when more than one encoding algorithm is considered.
Okay, point taken. Have any suggestions on how to make this easier on the
eyse for the user? If it's not provided by Cayenne, I see a lot of people
writing precisely that method. Encoding a List returned from a query will
most likely be a common idiom, and calling:
new XMLEncoder().encode(rootXmlTag, objects);
every time is going to be an eyesore, IMHO.
>> There are some other API changes that I'm not sure really make sense
>> either (e.g., having a public nodeToString() method).
>
> It is not public.
My bad. I looked at the unit tests, particularly
XMLEncoderTst#testEncodeSimpleCollection(), it appeared this may be a way
to encode things. I then browsed the source quickly, but wasn't paying
much attention to access modifiers.
I guess that's all I've got for now.
Thanks for the reply,
Kevin
This archive was generated by hypermail 2.0.0 : Mon Dec 05 2005 - 06:54:26 EST