> > The thing to know about tapestry-hibernate is that it creates a proxy > for the actual hibernate session. When you use the injected session it > actually gets the session for the current thread, via the > HibernateSessionManager I believe. So when you instantiate your DAO with > a session in the constructor, they will always get the session for the > current thread transparently.
Hi Chris, this clears up a lot for me. Thanks! regards, Onno
