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]
