| 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 or - preferably -
Hibernate's own SessionFactory.getCurrentSession() method, to be
able to detect a thread-bound Session. Typically, the code will look like as follows:
public void doSomeDataAccessAction() {
Session session = this.sessionFactory.getCurrentSession();
...
// No need to close the Session or translate exceptions!
}
Note that this interceptor automatically translates HibernateExceptions,
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).
This can be turned off if the raw exceptions are preferred.
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 drawback is the dependency on interceptor configuration. However, note
that this interceptor is usually not necessary in scenarios where the
data access code always executes within transactions. A transaction will always
have a thread-bound Session in the first place, so adding this interceptor to the
configuration just adds value when fine-tuning Session settings like the flush mode
- or when relying on exception translation.
author:
Juergen Hoeller
since:
1.2
See Also: org.hibernate.SessionFactory.getCurrentSession
See Also: HibernateTransactionManager
See Also: HibernateTemplate | 