hivemind-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Carman" <>
Subject RE: Hivetranse/Hibernate/Tapestry troubles
Date Thu, 02 Mar 2006 15:23:01 GMT
I would probably use the code from Honeycomb, as it is based on what I have
written and is more likely to be maintained.  I only put that out there as
an example.  I'm actually not using HiveUtils anymore.  I'm the crazy guy
who's trying to get Spring's classes to work in HiveMind! :-o

-----Original Message-----
From: Andreas Bulling [] On Behalf Of
Andreas Bulling
Sent: Thursday, March 02, 2006 10:18 AM
Subject: Re: Hivetranse/Hibernate/Tapestry troubles

Hi James,

thanks a lot for your explanations! Perhaps I will use your code but
as somebody on the tapestry-user list mentioned perhaps I will also
use the code from honeycomb. I will see ;)


On 01. Mär 2006 - 19:14:28, James Carman wrote:
| 1.  The reason to use the EntityPropertyPersistenceStrategy is so that you
| avoid trying to access "detached" objects.  The objects themselves are not
| stored in the session (if they're actually persistent), their identities
| (classname and id value).  Then, when your request comes in, the
| are resolved back into the real object in the current session.
| 2.  The same sort of thing is true for the "squeezer."  The squeezer
| write the entire object out to the client, it only writes its identity.
| main reason for this (besides detached objects) is that you want to avoid
| writing the entire object graph out to the client.  Imagine a highly
| connected domain model where each object is connected to other objects and
| so on and so on (and they tell two friends, and so on, and so on).
| when you go to serialize that, all of the references to other objects will
| be serialized to and you could end up with the entire database (worst case
| of course) being serialized out to the client.  YUCK!
| 3.  As far as the OpenSessionInViewFilter, it really shouldn't be needed
| with HiveUtils.  The session is supposed to be opened "as needed", but in
| experience, it wasn't. 

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message