I've used the long session pattern. It works really well at avoiding
lazy exceptions and whatnot. You do need to be careful though not to clutter
up your session with unnecessary persistent objects or you end up
serializing a whopping big entity whenever the Visit gets serialized.
--- Pat
> -----Original Message-----
> From: Henri Dupre [mailto:[EMAIL PROTECTED]
> Sent: Thursday, September 22, 2005 12:25 PM
> To: Tapestry users
> Subject: Hibernate session model
>
> Has anyone implemented a different Hibernate session model than the
> per-request with Tapestry?
> We are currently using a per-request one (with the Spring Hibernate
> filter) but I'm considering a per-websession model (store the
> Hibernate session in the Visit). We are running into some complex
> LazyExceptions and I don't see any advantage of using a per-session
> model.
> Any experiences?
>
> Thanks,
>
> Henri.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
