|
From: <Jon...@o2...> - 2005-07-11 11:06:18
|
* <p>Supports custom isolation levels, and timeouts that get applied as appropriate * Hibernate query timeouts. To support the latter, application code must either use * one of the <code>HibernateTemplate.find</code> methods or call * <code>SessionFactoryUtils.applyTransactionTimeout</code> for each created * Hibernate Query object. From what I think, SessionFactoryUtils.applyTransactionTimeout must only be called when exposeNativeSession is true (unless using HibernateTemplate.find). Otherwise session proxy will be created and CloseSuppressingInvocationHandler will prepare any Query or Criteria object created from that session just fine. This is a cool feature, so maybe javadoc should be more detailed here? I was already seeing myself going through various DAOs and adopting each and every method just because I want to introduce connection timeouts... Regards, Jonas |