当前页面:
在线文档首页 >
Spring Framework 1.2.9 API 文档英文版
HibernateInterceptor (Spring Framework) - Spring Framework 1.2.9 API 文档英文版
org.springframework.orm.hibernate
Class HibernateInterceptor
java.lang.Object
org.springframework.orm.hibernate.HibernateAccessor
org.springframework.orm.hibernate.HibernateInterceptor
- All Implemented Interfaces:
- Advice, Interceptor, MethodInterceptor, BeanFactoryAware, InitializingBean
public class HibernateInterceptor
- extends HibernateAccessor
- implements MethodInterceptor
This interceptor binds a new Hibernate Session to the thread before a method
call, closing and removing it afterwards in case of any method outcome.
If there already is a pre-bound Session (e.g. from HibernateTransactionManager,
or from a surrounding Hibernate-intercepted method), the interceptor simply
participates in it.
Application code must retrieve a Hibernate Session via the
SessionFactoryUtils.getSession method, to be able to detect a
thread-bound Session. It is preferable to use getSession with
allowCreate=false, if the code relies on the interceptor to provide proper
Session handling. Typically, the code will look like as follows:
public void doHibernateAction() {
Session session = SessionFactoryUtils.getSession(this.sessionFactory, false);
try {
...
}
catch (HibernateException ex) {
throw SessionFactoryUtils.convertHibernateAccessException(ex);
}
}
Note that the application must care about handling HibernateExceptions itself,
preferably via delegating to the
SessionFactoryUtils.convertHibernateAccessException
method that converts them to exceptions that are compatible with the
org.springframework.dao exception hierarchy (like HibernateTemplate does).
Unfortunately, this interceptor cannot convert checked HibernateExceptions
to unchecked dao ones transparently. The intercepted method would have to declare
the checked HibernateException - thus the caller would still have to catch or
rethrow it, even if it will never be thrown if intercepted. Any such exception
will nevertheless get converted by default.
This class can be considered a declarative alternative to HibernateTemplate's
callback approach. The advantages are:
- no anonymous classes necessary for callback implementations;
- the possibility to throw any application exceptions from within data access code.
The drawbacks are:
- the dependency on interceptor configuration;
- the delegating try/catch blocks.
Note: Spring's Hibernate support requires Hibernate 2.1 (as of Spring 1.0).
- Since:
- 13.06.2003
- Author:
- Juergen Hoeller
- See Also:
SessionFactoryUtils.getSession(net.sf.hibernate.SessionFactory, boolean),
HibernateTransactionManager,
HibernateTemplate
| Methods inherited from class org.springframework.orm.hibernate.HibernateAccessor |
afterPropertiesSet, applyFlushMode, convertHibernateAccessException, convertJdbcAccessException, convertJdbcAccessException, flushIfNecessary, getEntityInterceptor, getFlushMode, getJdbcExceptionTranslator, getSessionFactory, setBeanFactory, setEntityInterceptor, setEntityInterceptorBeanName, setFlushMode, setFlushModeName, setJdbcExceptionTranslator, setSessionFactory |
| Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
HibernateInterceptor
public HibernateInterceptor()
invoke
public Object invoke(MethodInvocation methodInvocation)
throws Throwable
- Specified by:
invoke in interface MethodInterceptor
- Throws:
Throwable
getSession
protected net.sf.hibernate.Session getSession()
- Return a Session for use by this interceptor.
- See Also:
SessionFactoryUtils.getSession(net.sf.hibernate.SessionFactory, boolean)
Copyright (c) 2002-2007 The Spring Framework Project.
