Hi,

I have an application that has a lot of hibernate detached objects
(with lazy loaded collections) that are persistent page properties. 
What are best practices for reattaching these detached objects while
maintaining a clean separation of layers?  I have my implementation
specific persistence layer separated into DAOs, a service layer, and
the tapestry ui layer.  I would like to keep tapestry independent of
the persistence layer.  I am using the OpenSessionInView pattern to
open a new hibernate session for each web request.  However, I can't
determine a clean way to reattach all the hibernate detached objects
at the beginning of each web request.  I've noticed that some people
use pageBeginRender() to reattach objects, but I don't want to expose
my tapestry code to the persistence implementation.  An interceptor or
filter or something that separated the ui layer from being aware of
the persistence layer would be ideal.  How have others dealt with this
issue?

Thanks,
Anthony

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to