RE: Possible Max Size Problem? -repost

Thanks for the input guys!

        But, I already am changing all the sets into new sets since I do some string manipulation of the data held in these sets before I send them over the wire. So for each equipment I grab the equipkey set, create a fresh set, manipulate strings, and load em in new set. Then set the equipments set to the new set.

I really don't know how much data I am sending. Has anyone sent a rather large amount of data with Hessian? I just really cant understand what else it could be.

Adrian

-----Original Message-----
From: owner-hessian-interest@xxx.com [mailto:owner-hessian-interest@xxx.com] On Behalf Of Radu-Adrian Popescu
Sent: Wednesday, January 19, 2005 10:11 AM
To: hessian-interest@xxx.com
Subject: Re: Possible Max Size Problem? -repost

Off-topic below:

Manolo Gómez P. wrote:
> Yes, it is as Victor says, Hibernate uses it's own implementation
> around collection classes because it needs to control changes in
> containing objects.
>

too much magick.

> I can quite remember, but I think this collections are enhanced using
> either reflection or bytecode enhancing (cglib2).
>
> OK, maybe just cloning the collection would do, but if your list has
> an internal set, then that set may be a Hibernate enhanced collection
> too, in which case you probably need to clone it too.
>

Depending on the clone type (deep/shallow) that could be quite a performance
hit, not to mention that the whole idea of copying data from a collection that's
nice and merry for your code into another that mirrors it for data transfer is
such a very wrong and wasteful thing to do.
You may be better off using iBATIS if you're in the first stages of development,
as it's very neat and does not f#*@ with you in such devious ways.

> Just a thought.
>

Yeah, mine too, I guess it worth 2c only to myself :)
Good luck,

-- 
Radu-Adrian Popescu
CSA, DBA, Developer
Aldrapay MD
Aldratech Ltd.
+40213212243