类 HibernateTransactionManager
- java.lang.Object
- org.springframework.transaction.support.AbstractPlatformTransactionManager
- org.springframework.orm.hibernate3.HibernateTransactionManager
- 所有已实现的接口:
Serializable
,Aware
,BeanFactoryAware
,InitializingBean
,PlatformTransactionManager
,ResourceTransactionManager
@Deprecated public class HibernateTransactionManager extends AbstractPlatformTransactionManager implements ResourceTransactionManager, BeanFactoryAware, InitializingBean
已过时。as of Spring 4.3, in favor of Hibernate 4.x/5.xPlatformTransactionManager
implementation for a single HibernateSessionFactory
. Binds a Hibernate Session from the specified factory to the thread, potentially allowing for one thread-bound Session per factory.SessionFactoryUtils
andHibernateTemplate
are aware of thread-bound Sessions and participate in such transactions automatically. Using either of those or going throughSessionFactory.getCurrentSession()
is required for Hibernate access code that needs to support this transaction handling mechanism.Supports custom isolation levels, and timeouts that get applied as Hibernate transaction timeouts.
This transaction manager is appropriate for applications that use a single Hibernate SessionFactory for transactional data access, but it also supports direct DataSource access within a transaction (i.e. plain JDBC code working with the same DataSource). This allows for mixing services which access Hibernate and services which use plain JDBC (without being aware of Hibernate)! Application code needs to stick to the same simple Connection lookup pattern as with
DataSourceTransactionManager
(i.e.DataSourceUtils.getConnection(javax.sql.DataSource)
or going through aTransactionAwareDataSourceProxy
).Note: To be able to register a DataSource's Connection for plain JDBC code, this instance needs to be aware of the DataSource (
setDataSource(javax.sql.DataSource)
). The given DataSource should obviously match the one used by the given SessionFactory. To achieve this, configure both to the same JNDI DataSource, or preferably create the SessionFactory withLocalSessionFactoryBean
and a local DataSource (which will be autodetected by this transaction manager).JTA (usually through
JtaTransactionManager
) is necessary for accessing multiple transactional resources within the same transaction. The DataSource that Hibernate uses needs to be JTA-enabled in such a scenario (see container setup). Normally, JTA setup for Hibernate is somewhat container-specific due to the JTA TransactionManager lookup, required for proper transactional handling of the SessionFactory-level read-write cache.Fortunately, there is an easier way with Spring:
SessionFactoryUtils
(and thusHibernateTemplate
) registers synchronizations with Spring'sTransactionSynchronizationManager
(as used byJtaTransactionManager
), for proper after-completion callbacks. Therefore, as long as Spring's JtaTransactionManager drives the JTA transactions, Hibernate does not require any special configuration for proper JTA participation. Note that there are special restrictions with EJB CMT and restrictive JTA subsystems: SeeJtaTransactionManager
's javadoc for details.This transaction manager supports nested transactions via JDBC 3.0 Savepoints. The
AbstractPlatformTransactionManager.setNestedTransactionAllowed(boolean)
"nestedTransactionAllowed"} flag defaults to "false", though, as nested transactions will just apply to the JDBC Connection, not to the Hibernate Session and its cached entity objects and related context. You can manually set the flag to "true" if you want to use nested transactions for JDBC access code which participates in Hibernate transactions (provided that your JDBC driver supports Savepoints). Note that Hibernate itself does not support nested transactions! Hence, do not expect Hibernate access code to semantically participate in a nested transaction.Requires Hibernate 3.6.x, as of Spring 4.0.
- 从以下版本开始:
- 1.2
- 作者:
- Juergen Hoeller
- 另请参阅:
setSessionFactory(org.hibernate.SessionFactory)
,setDataSource(javax.sql.DataSource)
,LocalSessionFactoryBean
,SessionFactoryUtils.getSession(org.hibernate.SessionFactory, boolean)
,SessionFactoryUtils.applyTransactionTimeout(org.hibernate.Query, org.hibernate.SessionFactory)
,SessionFactoryUtils.releaseSession(org.hibernate.Session, org.hibernate.SessionFactory)
,HibernateTemplate
,SessionFactory.getCurrentSession()
,DataSourceUtils.getConnection(javax.sql.DataSource)
,DataSourceUtils.applyTransactionTimeout(java.sql.Statement, javax.sql.DataSource)
,DataSourceUtils.releaseConnection(java.sql.Connection, javax.sql.DataSource)
,JdbcTemplate
,DataSourceTransactionManager
,JtaTransactionManager
, 序列化表格
字段概要
从类继承的字段 org.springframework.transaction.support.AbstractPlatformTransactionManager
logger, SYNCHRONIZATION_ALWAYS, SYNCHRONIZATION_NEVER, SYNCHRONIZATION_ON_ACTUAL_TRANSACTION
构造器概要
构造器 构造器 说明 HibernateTransactionManager()
已过时。Create a new HibernateTransactionManager instance.HibernateTransactionManager(SessionFactory sessionFactory)
已过时。Create a new HibernateTransactionManager instance.
方法概要
所有方法 实例方法 具体方法 已过时的方法 修饰符和类型 方法 说明 void
afterPropertiesSet()
已过时。Invoked by the containingBeanFactory
after it has set all bean properties and satisfiedBeanFactoryAware
,ApplicationContextAware
etc.protected DataAccessException
convertHibernateAccessException(HibernateException ex)
已过时。Convert the given HibernateException to an appropriate exception from theorg.springframework.dao
hierarchy.protected DataAccessException
convertJdbcAccessException(JDBCException ex, SQLExceptionTranslator translator)
已过时。Convert the given Hibernate JDBCException to an appropriate exception from theorg.springframework.dao
hierarchy, using the given SQLExceptionTranslator.protected void
doBegin(Object transaction, TransactionDefinition definition)
已过时。Begin a new transaction with semantics according to the given transaction definition.protected void
doCleanupAfterCompletion(Object transaction)
已过时。Cleanup resources after transaction completion.protected void
doCommit(DefaultTransactionStatus status)
已过时。Perform an actual commit of the given transaction.protected Object
doGetTransaction()
已过时。Return a transaction object for the current transaction state.protected void
doResume(Object transaction, Object suspendedResources)
已过时。Resume the resources of the current transaction.protected void
doRollback(DefaultTransactionStatus status)
已过时。Perform an actual rollback of the given transaction.protected void
doSetRollbackOnly(DefaultTransactionStatus status)
已过时。Set the given transaction rollback-only.protected Object
doSuspend(Object transaction)
已过时。Suspend the resources of the current transaction.DataSource
getDataSource()
已过时。Return the JDBC DataSource that this instance manages transactions for.protected SQLExceptionTranslator
getDefaultJdbcExceptionTranslator()
已过时。Obtain a default SQLExceptionTranslator, lazily creating it if necessary.Interceptor
getEntityInterceptor()
已过时。Return the current Hibernate entity interceptor, ornull
if none.SQLExceptionTranslator
getJdbcExceptionTranslator()
已过时。Return the JDBC exception translator for this transaction manager, if any.Object
getResourceFactory()
已过时。Return the resource factory that this transaction manager operates on, e.g. a JDBC DataSource or a JMS ConnectionFactory.SessionFactory
getSessionFactory()
已过时。Return the SessionFactory that this instance should manage transactions for.protected boolean
isExistingTransaction(Object transaction)
已过时。Check if the given transaction object indicates an existing transaction (that is, a transaction which has already started).protected boolean
isSameConnectionForEntireSession(Session session)
已过时。Return whether the given Hibernate Session will always hold the same JDBC Connection.protected void
prepareForCommit(DefaultTransactionStatus status)
已过时。Make preparations for commit, to be performed before thebeforeCommit
synchronization callbacks occur.void
setAutodetectDataSource(boolean autodetectDataSource)
已过时。Set whether to autodetect a JDBC DataSource used by the Hibernate SessionFactory, if set via LocalSessionFactoryBean'ssetDataSource
.void
setBeanFactory(BeanFactory beanFactory)
已过时。The bean factory just needs to be known for resolving entity interceptor bean names.void
setDataSource(DataSource dataSource)
已过时。Set the JDBC DataSource that this instance should manage transactions for.void
setEarlyFlushBeforeCommit(boolean earlyFlushBeforeCommit)
已过时。Set whether to perform an early flush before proceeding with a commit.void
setEntityInterceptor(Interceptor entityInterceptor)
已过时。Set a Hibernate entity interceptor that allows to inspect and change property values before writing to and reading from the database.void
setEntityInterceptorBeanName(String entityInterceptorBeanName)
已过时。Set the bean name of a Hibernate entity interceptor that allows to inspect and change property values before writing to and reading from the database.void
setHibernateManagedSession(boolean hibernateManagedSession)
已过时。Set whether to operate on a Hibernate-managed Session instead of a Spring-managed Session, that is, whether to obtain the Session through Hibernate'sSessionFactory.getCurrentSession()
instead ofSessionFactory.openSession()
(with a SpringTransactionSynchronizationManager
check preceding it).void
setJdbcExceptionTranslator(SQLExceptionTranslator jdbcExceptionTranslator)
已过时。Set the JDBC exception translator for this transaction manager.void
setPrepareConnection(boolean prepareConnection)
已过时。Set whether to prepare the underlying JDBC Connection of a transactional Hibernate Session, that is, whether to apply a transaction-specific isolation level and/or the transaction's read-only flag to the underlying JDBC Connection.void
setSessionFactory(SessionFactory sessionFactory)
已过时。Set the SessionFactory that this instance should manage transactions for.从类继承的方法 org.springframework.transaction.support.AbstractPlatformTransactionManager
commit, determineTimeout, getDefaultTimeout, getTransaction, getTransactionSynchronization, invokeAfterCompletion, isFailEarlyOnGlobalRollbackOnly, isGlobalRollbackOnParticipationFailure, isNestedTransactionAllowed, isRollbackOnCommitFailure, isValidateExistingTransaction, newTransactionStatus, prepareSynchronization, prepareTransactionStatus, registerAfterCompletionWithExistingTransaction, resume, rollback, setDefaultTimeout, setFailEarlyOnGlobalRollbackOnly, setGlobalRollbackOnParticipationFailure, setNestedTransactionAllowed, setRollbackOnCommitFailure, setTransactionSynchronization, setTransactionSynchronizationName, setValidateExistingTransaction, shouldCommitOnGlobalRollbackOnly, suspend, triggerBeforeCommit, triggerBeforeCompletion, useSavepointForNestedTransaction
从类继承的方法 java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
从接口继承的方法 org.springframework.transaction.PlatformTransactionManager
commit, getTransaction, rollback
构造器详细资料
HibernateTransactionManager
public HibernateTransactionManager()
已过时。Create a new HibernateTransactionManager instance. A SessionFactory has to be set to be able to use it.
HibernateTransactionManager
public HibernateTransactionManager(SessionFactory sessionFactory)
已过时。Create a new HibernateTransactionManager instance.- 参数:
sessionFactory
- SessionFactory to manage transactions for
方法详细资料
setSessionFactory
public void setSessionFactory(SessionFactory sessionFactory)
已过时。Set the SessionFactory that this instance should manage transactions for.
getSessionFactory
public SessionFactory getSessionFactory()
已过时。Return the SessionFactory that this instance should manage transactions for.
setDataSource
public void setDataSource(DataSource dataSource)
已过时。Set the JDBC DataSource that this instance should manage transactions for. The DataSource should match the one used by the Hibernate SessionFactory: for example, you could specify the same JNDI DataSource for both.If the SessionFactory was configured with LocalDataSourceConnectionProvider, i.e. by Spring's LocalSessionFactoryBean with a specified "dataSource", the DataSource will be auto-detected: You can still explicitly specify the DataSource, but you don't need to in this case.
A transactional JDBC Connection for this DataSource will be provided to application code accessing this DataSource directly via DataSourceUtils or JdbcTemplate. The Connection will be taken from the Hibernate Session.
The DataSource specified here should be the target DataSource to manage transactions for, not a TransactionAwareDataSourceProxy. Only data access code may work with TransactionAwareDataSourceProxy, while the transaction manager needs to work on the underlying target DataSource. If there's nevertheless a TransactionAwareDataSourceProxy passed in, it will be unwrapped to extract its target DataSource.
getDataSource
public DataSource getDataSource()
已过时。Return the JDBC DataSource that this instance manages transactions for.
setAutodetectDataSource
public void setAutodetectDataSource(boolean autodetectDataSource)
已过时。Set whether to autodetect a JDBC DataSource used by the Hibernate SessionFactory, if set via LocalSessionFactoryBean'ssetDataSource
. Default is "true".Can be turned off to deliberately ignore an available DataSource, in order to not expose Hibernate transactions as JDBC transactions for that DataSource.
setPrepareConnection
public void setPrepareConnection(boolean prepareConnection)
已过时。Set whether to prepare the underlying JDBC Connection of a transactional Hibernate Session, that is, whether to apply a transaction-specific isolation level and/or the transaction's read-only flag to the underlying JDBC Connection.Default is "true". If you turn this flag off, the transaction manager will not support per-transaction isolation levels anymore. It will not call
Connection.setReadOnly(true)
for read-only transactions anymore either. If this flag is turned off, no cleanup of a JDBC Connection is required after a transaction, since no Connection settings will get modified.
setHibernateManagedSession
public void setHibernateManagedSession(boolean hibernateManagedSession)
已过时。Set whether to operate on a Hibernate-managed Session instead of a Spring-managed Session, that is, whether to obtain the Session through Hibernate'sSessionFactory.getCurrentSession()
instead ofSessionFactory.openSession()
(with a SpringTransactionSynchronizationManager
check preceding it).Default is "false", i.e. using a Spring-managed Session: taking the current thread-bound Session if available (e.g. in an Open-Session-in-View scenario), creating a new Session for the current transaction otherwise.
Switch this flag to "true" in order to enforce use of a Hibernate-managed Session. Note that this requires
SessionFactory.getCurrentSession()
to always return a proper Session when called for a Spring-managed transaction; transaction begin will fail if thegetCurrentSession()
call fails.This mode will typically be used in combination with a custom Hibernate
CurrentSessionContext
implementation that stores Sessions in a place other than Spring's TransactionSynchronizationManager. It may also be used in combination with Spring's Open-Session-in-View support (using Spring's defaultSpringSessionContext
), in which case it subtly differs from the Spring-managed Session mode: The pre-bound Session will not receive aclear()
call (on rollback) or adisconnect()
call (on transaction completion) in such a scenario; this is rather left up to a custom CurrentSessionContext implementation (if desired).
setEarlyFlushBeforeCommit
public void setEarlyFlushBeforeCommit(boolean earlyFlushBeforeCommit)
已过时。Set whether to perform an early flush before proceeding with a commit.Default is "false", performing an implicit flush as part of the actual commit step. Switch this to "true" in order to enforce an explicit early flush right before the actual commit step.
An early flush happens before the before-commit synchronization phase, making flushed state visible to
beforeCommit
callbacks of registeredTransactionSynchronization
objects. Such explicit flush behavior is consistent with Spring-driven flushing in a JTA transaction environment, so may also get enforced for consistency with JTA transaction behavior.
setEntityInterceptorBeanName
public void setEntityInterceptorBeanName(String entityInterceptorBeanName)
已过时。Set the bean name of a Hibernate entity interceptor that allows to inspect and change property values before writing to and reading from the database. Will get applied to any new Session created by this transaction manager.Requires the bean factory to be known, to be able to resolve the bean name to an interceptor instance on session creation. Typically used for prototype interceptors, i.e. a new interceptor instance per session.
Can also be used for shared interceptor instances, but it is recommended to set the interceptor reference directly in such a scenario.
- 参数:
entityInterceptorBeanName
- the name of the entity interceptor in the bean factory- 另请参阅:
setBeanFactory(org.springframework.beans.factory.BeanFactory)
,setEntityInterceptor(org.hibernate.Interceptor)
setEntityInterceptor
public void setEntityInterceptor(Interceptor entityInterceptor)
已过时。Set a Hibernate entity interceptor that allows to inspect and change property values before writing to and reading from the database. Will get applied to any new Session created by this transaction manager.Such an interceptor can either be set at the SessionFactory level, i.e. on LocalSessionFactoryBean, or at the Session level, i.e. on HibernateTemplate, HibernateInterceptor, and HibernateTransactionManager. It's preferable to set it on LocalSessionFactoryBean or HibernateTransactionManager to avoid repeated configuration and guarantee consistent behavior in transactions.
getEntityInterceptor
public Interceptor getEntityInterceptor() throws IllegalStateException, BeansException
已过时。Return the current Hibernate entity interceptor, ornull
if none. Resolves an entity interceptor bean name via the bean factory, if necessary.- 抛出:
IllegalStateException
- if bean name specified but no bean factory setBeansException
- if bean name resolution via the bean factory failed- 另请参阅:
setEntityInterceptor(org.hibernate.Interceptor)
,setEntityInterceptorBeanName(java.lang.String)
,setBeanFactory(org.springframework.beans.factory.BeanFactory)
setJdbcExceptionTranslator
public void setJdbcExceptionTranslator(SQLExceptionTranslator jdbcExceptionTranslator)
已过时。Set the JDBC exception translator for this transaction manager.Applied to any SQLException root cause of a Hibernate JDBCException that is thrown on flush, overriding Hibernate's default SQLException translation (which is based on Hibernate's Dialect for a specific target database).
- 参数:
jdbcExceptionTranslator
- the exception translator- 另请参阅:
SQLException
,JDBCException
,SQLErrorCodeSQLExceptionTranslator
,SQLStateSQLExceptionTranslator
getJdbcExceptionTranslator
public SQLExceptionTranslator getJdbcExceptionTranslator()
已过时。Return the JDBC exception translator for this transaction manager, if any.
setBeanFactory
public void setBeanFactory(BeanFactory beanFactory)
已过时。The bean factory just needs to be known for resolving entity interceptor bean names. It does not need to be set for any other mode of operation.- 指定者:
setBeanFactory
在接口中BeanFactoryAware
- 参数:
beanFactory
- owning BeanFactory (nevernull
). The bean can immediately call methods on the factory.- 另请参阅:
setEntityInterceptorBeanName(java.lang.String)
afterPropertiesSet
public void afterPropertiesSet()
已过时。从接口复制的说明:InitializingBean
Invoked by the containingBeanFactory
after it has set all bean properties and satisfiedBeanFactoryAware
,ApplicationContextAware
etc.This method allows the bean instance to perform validation of its overall configuration and final initialization when all bean properties have been set.
- 指定者:
afterPropertiesSet
在接口中InitializingBean
getResourceFactory
public Object getResourceFactory()
已过时。从接口复制的说明:ResourceTransactionManager
Return the resource factory that this transaction manager operates on, e.g. a JDBC DataSource or a JMS ConnectionFactory.This target resource factory is usually used as resource key for
TransactionSynchronizationManager
's resource bindings per thread.- 指定者:
getResourceFactory
在接口中ResourceTransactionManager
- 返回:
- the target resource factory (never
null
) - 另请参阅:
TransactionSynchronizationManager.bindResource(java.lang.Object, java.lang.Object)
,TransactionSynchronizationManager.getResource(java.lang.Object)
doGetTransaction
protected Object doGetTransaction()
已过时。从类复制的说明:AbstractPlatformTransactionManager
Return a transaction object for the current transaction state.The returned object will usually be specific to the concrete transaction manager implementation, carrying corresponding transaction state in a modifiable fashion. This object will be passed into the other template methods (e.g. doBegin and doCommit), either directly or as part of a DefaultTransactionStatus instance.
The returned object should contain information about any existing transaction, that is, a transaction that has already started before the current
getTransaction
call on the transaction manager. Consequently, adoGetTransaction
implementation will usually look for an existing transaction and store corresponding state in the returned transaction object.- 指定者:
doGetTransaction
在类中AbstractPlatformTransactionManager
- 返回:
- the current transaction object
- 另请参阅:
AbstractPlatformTransactionManager.doBegin(java.lang.Object, org.springframework.transaction.TransactionDefinition)
,AbstractPlatformTransactionManager.doCommit(org.springframework.transaction.support.DefaultTransactionStatus)
,AbstractPlatformTransactionManager.doRollback(org.springframework.transaction.support.DefaultTransactionStatus)
,DefaultTransactionStatus.getTransaction()
isExistingTransaction
protected boolean isExistingTransaction(Object transaction)
已过时。从类复制的说明:AbstractPlatformTransactionManager
Check if the given transaction object indicates an existing transaction (that is, a transaction which has already started).The result will be evaluated according to the specified propagation behavior for the new transaction. An existing transaction might get suspended (in case of PROPAGATION_REQUIRES_NEW), or the new transaction might participate in the existing one (in case of PROPAGATION_REQUIRED).
The default implementation returns
false
, assuming that participating in existing transactions is generally not supported. Subclasses are of course encouraged to provide such support.- 覆盖:
isExistingTransaction
在类中AbstractPlatformTransactionManager
- 参数:
transaction
- transaction object returned by doGetTransaction- 返回:
- if there is an existing transaction
- 另请参阅:
AbstractPlatformTransactionManager.doGetTransaction()
doBegin
protected void doBegin(Object transaction, TransactionDefinition definition)
已过时。从类复制的说明:AbstractPlatformTransactionManager
Begin a new transaction with semantics according to the given transaction definition. Does not have to care about applying the propagation behavior, as this has already been handled by this abstract manager.This method gets called when the transaction manager has decided to actually start a new transaction. Either there wasn't any transaction before, or the previous transaction has been suspended.
A special scenario is a nested transaction without savepoint: If
useSavepointForNestedTransaction()
returns "false", this method will be called to start a nested transaction when necessary. In such a context, there will be an active transaction: The implementation of this method has to detect this and start an appropriate nested transaction.- 指定者:
doBegin
在类中AbstractPlatformTransactionManager
- 参数:
transaction
- transaction object returned bydoGetTransaction
definition
- TransactionDefinition instance, describing propagation behavior, isolation level, read-only flag, timeout, and transaction name
doSuspend
protected Object doSuspend(Object transaction)
已过时。从类复制的说明:AbstractPlatformTransactionManager
Suspend the resources of the current transaction. Transaction synchronization will already have been suspended.The default implementation throws a TransactionSuspensionNotSupportedException, assuming that transaction suspension is generally not supported.
- 覆盖:
doSuspend
在类中AbstractPlatformTransactionManager
- 参数:
transaction
- transaction object returned bydoGetTransaction
- 返回:
- an object that holds suspended resources (will be kept unexamined for passing it into doResume)
- 另请参阅:
AbstractPlatformTransactionManager.doResume(java.lang.Object, java.lang.Object)
doResume
protected void doResume(Object transaction, Object suspendedResources)
已过时。从类复制的说明:AbstractPlatformTransactionManager
Resume the resources of the current transaction. Transaction synchronization will be resumed afterwards.The default implementation throws a TransactionSuspensionNotSupportedException, assuming that transaction suspension is generally not supported.
- 覆盖:
doResume
在类中AbstractPlatformTransactionManager
- 参数:
transaction
- transaction object returned bydoGetTransaction
suspendedResources
- the object that holds suspended resources, as returned by doSuspend- 另请参阅:
AbstractPlatformTransactionManager.doSuspend(java.lang.Object)
prepareForCommit
protected void prepareForCommit(DefaultTransactionStatus status)
已过时。从类复制的说明:AbstractPlatformTransactionManager
Make preparations for commit, to be performed before thebeforeCommit
synchronization callbacks occur.Note that exceptions will get propagated to the commit caller and cause a rollback of the transaction.
- 覆盖:
prepareForCommit
在类中AbstractPlatformTransactionManager
- 参数:
status
- the status representation of the transaction
doCommit
protected void doCommit(DefaultTransactionStatus status)
已过时。从类复制的说明:AbstractPlatformTransactionManager
Perform an actual commit of the given transaction.An implementation does not need to check the "new transaction" flag or the rollback-only flag; this will already have been handled before. Usually, a straight commit will be performed on the transaction object contained in the passed-in status.
- 指定者:
doCommit
在类中AbstractPlatformTransactionManager
- 参数:
status
- the status representation of the transaction- 另请参阅:
DefaultTransactionStatus.getTransaction()
doRollback
protected void doRollback(DefaultTransactionStatus status)
已过时。从类复制的说明:AbstractPlatformTransactionManager
Perform an actual rollback of the given transaction.An implementation does not need to check the "new transaction" flag; this will already have been handled before. Usually, a straight rollback will be performed on the transaction object contained in the passed-in status.
- 指定者:
doRollback
在类中AbstractPlatformTransactionManager
- 参数:
status
- the status representation of the transaction- 另请参阅:
DefaultTransactionStatus.getTransaction()
doSetRollbackOnly
protected void doSetRollbackOnly(DefaultTransactionStatus status)
已过时。从类复制的说明:AbstractPlatformTransactionManager
Set the given transaction rollback-only. Only called on rollback if the current transaction participates in an existing one.The default implementation throws an IllegalTransactionStateException, assuming that participating in existing transactions is generally not supported. Subclasses are of course encouraged to provide such support.
- 覆盖:
doSetRollbackOnly
在类中AbstractPlatformTransactionManager
- 参数:
status
- the status representation of the transaction
doCleanupAfterCompletion
protected void doCleanupAfterCompletion(Object transaction)
已过时。从类复制的说明:AbstractPlatformTransactionManager
Cleanup resources after transaction completion.Called after
doCommit
anddoRollback
execution, on any outcome. The default implementation does nothing.Should not throw any exceptions but just issue warnings on errors.
- 覆盖:
doCleanupAfterCompletion
在类中AbstractPlatformTransactionManager
- 参数:
transaction
- transaction object returned bydoGetTransaction
isSameConnectionForEntireSession
protected boolean isSameConnectionForEntireSession(Session session)
已过时。Return whether the given Hibernate Session will always hold the same JDBC Connection. This is used to check whether the transaction manager can safely prepare and clean up the JDBC Connection used for a transaction.Default implementation checks the Session's connection release mode to be "on_close". Unfortunately, this requires casting to SessionImpl, as of Hibernate 3.1. If that cast doesn't work, we'll simply assume we're safe and return
true
.- 参数:
session
- the Hibernate Session to check- 另请参阅:
SessionImpl.getConnectionReleaseMode()
,ConnectionReleaseMode.ON_CLOSE
convertHibernateAccessException
protected DataAccessException convertHibernateAccessException(HibernateException ex)
已过时。Convert the given HibernateException to an appropriate exception from theorg.springframework.dao
hierarchy.Will automatically apply a specified SQLExceptionTranslator to a Hibernate JDBCException, else rely on Hibernate's default translation.
- 参数:
ex
- HibernateException that occurred- 返回:
- a corresponding DataAccessException
- 另请参阅:
SessionFactoryUtils.convertHibernateAccessException(org.hibernate.HibernateException)
,setJdbcExceptionTranslator(org.springframework.jdbc.support.SQLExceptionTranslator)
convertJdbcAccessException
protected DataAccessException convertJdbcAccessException(JDBCException ex, SQLExceptionTranslator translator)
已过时。Convert the given Hibernate JDBCException to an appropriate exception from theorg.springframework.dao
hierarchy, using the given SQLExceptionTranslator.- 参数:
ex
- Hibernate JDBCException that occurredtranslator
- the SQLExceptionTranslator to use- 返回:
- a corresponding DataAccessException
getDefaultJdbcExceptionTranslator
protected SQLExceptionTranslator getDefaultJdbcExceptionTranslator()
已过时。Obtain a default SQLExceptionTranslator, lazily creating it if necessary.Creates a default
SQLErrorCodeSQLExceptionTranslator
for the SessionFactory's underlying DataSource.