《Spring 2.0技术手册》 读书笔记七-Spring的DAO框架(3)-JDBC事务管理
2011-03-13 20:46
666 查看
Spring提供了编程式事务管理(programmatic transaction management)与声明式事务管理(declarative transaction management)。由于编程式事务管理会导致Spring框架侵入代码,而且变更复杂,故不赞成使用编程式事务管理。因此该篇笔记以声明式事务管理为主。
事务是一组原子操作的工作单元,在数据库存取中,就是一组SQL指令,它们必须全部执行成功,因为某个原因未全部成功,则先前所有执行过的SQL指令都要被撤销。
1. JDBC的事务管理
其中,org.springframework.transaction.TransactionDefinition接口的实例定义了事务的隔离程度、传播行为、超时、只读等。
编程事务管理举例:
transactionManager、userDAO使用同一个DataSource,在org.springframework.transaction.interceptor.[b]TransactionProxyFactoryBean代理对象中设置被代理接口、被代理目标实例、事务管理器以及事务属性。这样事务管理会自动介入指定的方法前后。如上,userDAO中以insert开头的方法都会被纳入事务管理,即方法执行过程中发生错误,则方法中所有先前的操作都自动撤回,否则正常提交。
事务属性可以在TransactionDefinition接口中找到。对于目标方法可以加上多个事务属性定义,中间用","隔开。
这样配置后,就可以正常使用UserDAO了,在UserDAO类中不需要增加事务管理代码。即
IUserDAO dao=(IUserDAO)context.getBean("userDAOProxy");dao.insert(user);
也可以设置单独的Interceptor,如下:
<bean id="transactionInterceptor"
class="org.springframework.transaction.interceptor.TransactionInterceptor">
<property name="transactionManager" ref="transactionManager"/>
<property name="transactionAttributeSource"
value="org.spring.dao.UserDAO.insert*=PROPAGATION_REQUIRED"/>
</bean>
<bean id="userDAOProxy1"
class="org.springframework.aop.framework.ProxyFactoryBean">
<property name="proxyInterfaces">
<list>
<value>org.spring.dao.IUserDAO</value>
</list>
</property>
<property name="target" ref="userDAO"></property>
<property name="interceptorNames">
<list>
<value>transactionInterceptor</value>
</list>
</property>
</bean>
总结:Spring的学习笔记就到此结束了,基本内容概括的差不多了。随着学习和应用,会对Spring进行深层的补充和理解。
事务是一组原子操作的工作单元,在数据库存取中,就是一组SQL指令,它们必须全部执行成功,因为某个原因未全部成功,则先前所有执行过的SQL指令都要被撤销。
1. JDBC的事务管理
public interface PlatformTransactionManager { /** * Return a currently active transaction or create a new one, according to * the specified propagation behavior. * @param definition TransactionDefinition instance (can be <code>null</code> for defaults), * describing propagation behavior, isolation level, timeout etc. * @return transaction status object representing the new or current transaction */ TransactionStatus getTransaction(TransactionDefinition definition) throws TransactionException; /** * Commit the given transaction, with regard to its status. If the transaction * has been marked rollback-only programmatically, perform a rollback. * <p>If the transaction wasn't a new one, omit the commit for proper * participation in the surrounding transaction. If a previous transaction * has been suspended to be able to create a new one, resume the previous * transaction after committing the new one. * <p>Note that when the commit call completes, no matter if normally or * throwing an exception, the transaction must be fully completed and * cleaned up. No rollback call should be expected in such a case. * <p>If this method throws an exception other than a TransactionException, * then some before-commit error caused the commit attempt to fail. For * example, an O/R Mapping tool might have tried to flush changes to the * database right before commit, with the resulting DataAccessException * causing the transaction to fail. The original exception will be * propagated to the caller of this commit method in such a case. * @param status object returned by the <code>getTransaction</code> method */ void commit(TransactionStatus status) throws TransactionException; /** * Perform a rollback of the given transaction. * <p>If the transaction wasn't a new one, just set it rollback-only for proper * participation in the surrounding transaction. If a previous transaction * has been suspended to be able to create a new one, resume the previous * transaction after rolling back the new one. * <p><b>Do not call rollback on a transaction if commit threw an exception.</b> * The transaction will already have been completed and cleaned up when commit * returns, even in case of a commit exception. Consequently, a rollback call * after commit failure will lead to an IllegalTransactionStateException. * @param status object returned by the <code>getTransaction</code> method */ void rollback(TransactionStatus status) throws TransactionException; }
其中,org.springframework.transaction.TransactionDefinition接口的实例定义了事务的隔离程度、传播行为、超时、只读等。
public interface TransactionStatus extends SavepointManager { /** * Return whether the present transaction is new (else participating * in an existing transaction, or potentially not running in an * actual transaction in the first place). */ boolean isNewTransaction(); /** * Return whether this transaction internally carries a savepoint, * that is, has been created as nested transaction based on a savepoint. */ boolean hasSavepoint(); /** * Set the transaction rollback-only. This instructs the transaction manager * that the only possible outcome of the transaction may be a rollback, as * alternative to throwing an exception which would in turn trigger a rollback. */ void setRollbackOnly(); /** * Return whether the transaction has been marked as rollback-only * (either by the application or by the transaction infrastructure). */ boolean isRollbackOnly(); /** * Flush the underlying session to the datastore, if applicable: */ void flush(); /** * Return whether this transaction is completed, that is, * whether it has already been committed or rolled back. */ boolean isCompleted(); }
编程事务管理举例:
<bean id="transactionManager" class="org.springframework.jdbc.datasource.DataSourceTransactionManager"> <property name="dataSource" ref="dataSource"></property> </bean> <bean id="userDAO" class="org.spring.dao.UserDAO"> <property name="dataSource" ref="dataSource"></property> </bean> <bean id="userDAOProxy" class="org.springframework.transaction.interceptor.TransactionProxyFactoryBean"> <property name="proxyInterfaces"> <list> <value>org.spring.dao.IUserDAO</value> </list> </property> <property name="target" ref="userDAO"></property> <property name="transactionManager" ref="transactionManager"></property> <property name="transactionAttributes"> <props> <prop key="insert*">PROPAGATION_REQUIRED</prop> </props> </property> </bean>
transactionManager、userDAO使用同一个DataSource,在org.springframework.transaction.interceptor.[b]TransactionProxyFactoryBean代理对象中设置被代理接口、被代理目标实例、事务管理器以及事务属性。这样事务管理会自动介入指定的方法前后。如上,userDAO中以insert开头的方法都会被纳入事务管理,即方法执行过程中发生错误,则方法中所有先前的操作都自动撤回,否则正常提交。
事务属性可以在TransactionDefinition接口中找到。对于目标方法可以加上多个事务属性定义,中间用","隔开。
这样配置后,就可以正常使用UserDAO了,在UserDAO类中不需要增加事务管理代码。即
IUserDAO dao=(IUserDAO)context.getBean("userDAOProxy");dao.insert(user);
也可以设置单独的Interceptor,如下:
<bean id="transactionInterceptor"
class="org.springframework.transaction.interceptor.TransactionInterceptor">
<property name="transactionManager" ref="transactionManager"/>
<property name="transactionAttributeSource"
value="org.spring.dao.UserDAO.insert*=PROPAGATION_REQUIRED"/>
</bean>
<bean id="userDAOProxy1"
class="org.springframework.aop.framework.ProxyFactoryBean">
<property name="proxyInterfaces">
<list>
<value>org.spring.dao.IUserDAO</value>
</list>
</property>
<property name="target" ref="userDAO"></property>
<property name="interceptorNames">
<list>
<value>transactionInterceptor</value>
</list>
</property>
</bean>
总结:Spring的学习笔记就到此结束了,基本内容概括的差不多了。随着学习和应用,会对Spring进行深层的补充和理解。
相关文章推荐
- 《Spring 2.0技术手册》 读书笔记七-Spring的DAO框架(3)-JDBC事务管理
- 《Spring 2.0技术手册》 读书笔记七-Spring的DAO框架(3)-JDBC事务管理
- 《Spring 2.0技术手册》 读书笔记七-Spring的DAO框架(2)-JDBC支持
- 《Spring 2.0技术手册》 读书笔记七-Spring的DAO框架(2)-JDBC支持
- 《Spring 2.0技术手册》 读书笔记七-Spring的DAO框架(2)-JDBC支持
- 《Spring 2.0技术手册》 读书笔记七-Spring的DAO框架(1)-原理与DataSource注入
- 《Spring 2.0技术手册》 读书笔记七-Spring的DAO框架(1)-原理与DataSource注入
- 《Spring 2.0技术手册》 读书笔记七-Spring的DAO框架(1)-原理与DataSource注入
- Spring2.0中声明式事务管理(读spring2.0技术手册,林信良)
- springmvc+jdbc 声明式事务管理,适用于多种数据库框架
- Spring混合框架(Hibernate+JDBC/iBatis)的事务管理
- Spring2.0简明手册(系列之五 事务管理)
- Spring的事务管理难点剖析(1):DAO和事务管理的牵绊
- java 框架基础知识(7)----事务基础知识-->Spring事务管理
- 基于Spring的轻量级Web Service事务管理框架及其实现
- 《spring 2.0技术手册》的技术写作方式值得学习!
- springDAO中开启声明式事务管理套路
- Spring 框架的JDBC模板技术
- JDBC、JTA、Spring的事务管理
- 关于springIDE的安装与使用 【Spring2.0 技术手册补遗 】