对spring HibernateTemplate分析

研究spring的源代码主要是想搞明白 HibernateTemplate到底怎么样工作的.

在项目中经常会这样使用

public class ImpDateContinue extends HibernateDaoSupport implements DateContinueDAO { public Datecontinue getListForid(final int dcid) { return (Datecontinue) this.getHibernateTemplate().execute(new HibernateCallback(){ public Object doInHibernate(Session session){ Query q=session.createQuery("from Datecontinue as d where d.dcId=:dcId"); q.setInteger("dcId",dcid); return q.uniqueResult(); } }); } }

 

用HibernateCallback 回调的方法管理数据，为什么要这么做了？这样做的好处在于，首先对数据库的操作难免会用到对事务进行操作,涉及到事物操作就有一个对session进行打开关闭的问题,通过HibernateTemplate完全就不用担心session有没有关闭,资源有没有浪费,她可以正确的自动实现session的打开和关闭,并且自动参与事务操作。Template线程是安全的,可重用的,而且可作为外部类的实例变量打开而被保持。

HibernateTemplate源码

public Object execute(HibernateCallback action) throws DataAccessException { return execute(action, isExposeNativeSession()); } public List executeFind(HibernateCallback action) throws DataAccessException { Object result = execute(action, isExposeNativeSession()); if (result != null && !(result instanceof List)) { throw new InvalidDataAccessApiUsageException( "Result object returned from HibernateCallback isn't a List: [" + result + "]"); } return (List) result; } /** * Execute the action specified by the given action object within a Session. * @param action callback object that specifies the Hibernate action * @param exposeNativeSession whether to expose the native Hibernate Session * to callback code * @return a result object returned by the action, or <code>null</code> * @throws org.springframework.dao.DataAccessException in case of Hibernate errors */ public Object execute(HibernateCallback action, boolean exposeNativeSession) throws DataAccessException { Assert.notNull(action, "Callback object must not be null"); Session session = getSession(); boolean existingTransaction = SessionFactoryUtils.isSessionTransactional(session, getSessionFactory()); if (existingTransaction) { logger.debug("Found thread-bound Session for HibernateTemplate"); } FlushMode previousFlushMode = null; try { previousFlushMode = applyFlushMode(session, existingTransaction); enableFilters(session); Session sessionToExpose = (exposeNativeSession ? session : createSessionProxy(session)); Object result = action.doInHibernate(sessionToExpose); flushIfNecessary(session, existingTransaction); return result; } catch (HibernateException ex) { throw convertHibernateAccessException(ex); } catch (SQLException ex) { throw convertJdbcAccessException(ex); } catch (RuntimeException ex) { // Callback code threw application exception... throw ex; } finally { if (existingTransaction) { logger.debug("Not closing pre-bound Hibernate Session after HibernateTemplate"); disableFilters(session); if (previousFlushMode != null) { session.setFlushMode(previousFlushMode); } } else { // Never use deferred close for an explicitly new Session. if (isAlwaysUseNewSession()) { SessionFactoryUtils.closeSession(session); } else { SessionFactoryUtils.closeSessionOrRegisterDeferredClose(session, getSessionFactory()); } } } }

isSessionTransactional返回一个可操作事务的session,用HibernateCallback 回调管理数据.

SessionFactoryUtils

/** * Return whether the given Hibernate Session is transactional, that is, * bound to the current thread by Spring's transaction facilities. * @param session the Hibernate Session to check * @param sessionFactory Hibernate SessionFactory that the Session was created with * (may be <code>null</code>) * @return whether the Session is transactional */ public static boolean isSessionTransactional(Session session, SessionFactory sessionFactory) { if (sessionFactory == null) { return false; } SessionHolder sessionHolder = (SessionHolder) TransactionSynchronizationManager.getResource(sessionFactory); return (sessionHolder != null && sessionHolder.containsSession(session)); }

通过源码一分析所有困惑迎刃而解.在项目实际应用中可以这样配置，让Template去管理session ,操作事务。

<bean id="hibernateTemplate" class="org.springframework.orm.hibernate3.HibernateTemplate"> <property name="sessionFactory"> <ref bean="sessionFactorymysql" /> </property> </bean>