仍是接着xml方式自定义实现Ioc容器java
这个实例中,没有进行事务得操做,不能保持一个线程操做中事务得一致性;git
@Override public void transfer(String fromCardNo, String toCardNo, int money) throws Exception { Account from = accountDao.queryAccountByCardNo(fromCardNo); Account to = accountDao.queryAccountByCardNo(toCardNo); from.setMoney(from.getMoney()-money); to.setMoney(to.getMoney()+money); accountDao.updateAccountByCardNo(to); //模拟异常代码 int c = 1/0; accountDao.updateAccountByCardNo(from); }
service 层没有添加事务控制,这样会出现脏数据,可能会出现如下场景:github
解决这种脏数据问题是给service加上事务操做,若是出现异常,咱们就让他回滚,若是没有咱们就手动提交事务;数据库
当前线程2个update操做内的数据库操做属于同一个
线程
内执行调用,可让这个线程使用同一个数据库链接
1 如何让两个Update语句再同一个事务中呢!ide
在JDBC的事务操做中,必须操做的是同一个Connection链接
咱们可让两个update语句使用同一个数据库链接!ui
2 如何让让两个update语句使用同一个数据库链接?.net
Java中使用ThreadLocal
给当前线程绑定同一个对象线程
ThreadLocal<T> threadLocal = new ThreadLocal<>();
因此咱们来修改一下这行代码代理
Connection con = DruidUtils.getInstance().getConnection();
将获取链接部分抽离出来,定义一个链接工厂ConnetionUtil
类,单例它,保持一个对象,避免不一样得链接对事务影响;code
public class ConnetionUtil { //单例 保持惟一 private ConnetionUtil(){} private static ConnetionUtil connetionUtil = new ConnetionUtil(); public static ConnetionUtil getconnetionUtil(){ return connetionUtil; } private ThreadLocal<Connection> threadLocal = new ThreadLocal<>(); public Connection getConnection() throws SQLException { Connection connection = threadLocal.get(); if (threadLocal.get()==null){ connection = DruidUtils.getInstance().getConnection(); //绑定当前线程 数据库链接 threadLocal.set(connection); } //存在直接返回这个链接 return connection; } //开启事务 public void start() throws SQLException { //不自动提交 getConnection().setAutoCommit(false); } //提交事务 public void commit() throws SQLException { getConnection().commit(); } //关闭事务 回滚事务 public void rowback() throws SQLException { getConnection().rollback(); } public void close() throws SQLException { getConnection().close(); } }
而后再dao层去更改一下获取链接的地方
Connection con = ConnetionUtil.getconnetionUtil().getConnection();
而后再service层去控制事务,关闭自动事务提交,使用try..catch 捕获极可;
try { //开启事务 TransferServicemanager.get().start(); Account from = accountDao.queryAccountByCardNo(fromCardNo); Account to = accountDao.queryAccountByCardNo(toCardNo); from.setMoney(from.getMoney()-money); to.setMoney(to.getMoney()+money); accountDao.updateAccountByCardNo(to); //模拟异常代码 int c = 1/0; accountDao.updateAccountByCardNo(from); //提交事务 TransferServicemanager.get().commit(); }catch (Exception e){ //回滚事务 TransferServicemanager.get().rowback(); System.out.println(e.getStackTrace()); throw new RuntimeException("失败!"); }finally { //关闭链接 System.out.println(ConnetionUtil.getconnetionUtil()); ConnetionUtil.getconnetionUtil().close(); }
这样就能够实现手动控制事务,从而进一步保证数据一致性;
思考一下,平时工做中系统中有不少得写语句,那么每个业务层咱们都手动去加一下,事务控制代码,那不得被累死;
咱们须要改造一下,这块代码,使用代理去实现这块,动态的生成一个代理类去执行这块业务逻辑
基于类的职责,咱们定义一个事务管理器类TransferServicemanager
,将事务代码剥离出来,专门去管理事务操做!
public class TransferServicemanager { private TransferServicemanager(){} //单例 private static TransferServicemanager t = new TransferServicemanager(); //对外提供对象接口 public static TransferServicemanager get(){ return t; } //开启事务 public void start() throws SQLException { //不自动提交 ConnetionUtil.getconnetionUtil().start(); } //提交事务 public void commit() throws SQLException { ConnetionUtil.getconnetionUtil().commit(); } //关闭事务 回滚事务 public void rowback() throws SQLException { ConnetionUtil.getconnetionUtil().rowback(); } }
定义动态代理工厂ProxyFactory
类,这里经过传入的被代理对象,使用JDK和CGLIB去生成代理对象!
public class ProxyFactory { //单例 private ProxyFactory() { } private static ProxyFactory jdkProxy = new ProxyFactory(); //对外提供接口 public static ProxyFactory getJdkProxy() { return jdkProxy; } /** * Jdk动态代理 * * @param obj 被代理的对象 * @return 返回代理对象 */ public Object getJdkProxy(Object obj) { //生成代理对象 return Proxy.newProxyInstance(obj.getClass().getClassLoader(), obj.getClass().getInterfaces(), new InvocationHandler() { @Override public Object invoke(Object o, Method method, Object[] objects) throws Throwable { Object result = null; try { //开启事务 TransferServicemanager.get().start(); result = method.invoke(obj, objects); //提交事务 TransferServicemanager.get().commit(); } catch (Exception e) { //回滚事务 TransferServicemanager.get().rowback(); System.out.println(e.getStackTrace()); throw new RuntimeException("失败!"); } finally { //关闭链接 System.out.println(ConnetionUtil.getconnetionUtil()); ConnetionUtil.getconnetionUtil().close(); } return result; } }); } /** * Jdk动态代理 * * @param object 被代理的对象 * @return 返回代理对象 */ public Object getCglibProxy(Object object) { //生成代理对象 return Enhancer.create(object.getClass(), new MethodInterceptor() { @Override public Object intercept(Object o, Method method, Object[] objects, MethodProxy methodProxy) throws Throwable { Object result = null; try { //开启事务 TransferServicemanager.get().start(); result = method.invoke(object, objects); //提交事务 TransferServicemanager.get().commit(); } catch (Exception e) { //回滚事务 TransferServicemanager.get().rowback(); System.out.println(e.getStackTrace()); throw new RuntimeException("失败!"); } finally { //关闭链接 System.out.println(ConnetionUtil.getconnetionUtil()); ConnetionUtil.getconnetionUtil().close(); } return result; } }); } }
在代理类里执行原对象方法先后控制事务操做;
try { //开启事务 TransferServicemanager.get().start(); result = method.invoke(object, objects); //提交事务 TransferServicemanager.get().commit(); } catch (Exception e) { //回滚事务 TransferServicemanager.get().rowback(); System.out.println(e.getStackTrace()); throw new RuntimeException("失败!"); } finally { //关闭链接 System.out.println(ConnetionUtil.getconnetionUtil()); ConnetionUtil.getconnetionUtil().close(); } return result; }
最后在控制层去获取找个代理对象去执行方法
委托对象是加强了事务控制的功能(这个对象就已经加强了事务操做)
// 3 从工厂获取 // 3.1 获取jdk代理对象 ProxyFactory private TransferService transferService = (TransferService) ProxyFactory.getJdkProxy().getJdkProxy(BeanFactorys.getBean("transferService")); // 3.2 获取cglib 代理对象 ProxyFactory // private TransferServiceImpl transferService = (TransferServiceImpl) ProxyFactory.getJdkProxy().getCglibProxy(BeanFactorys.getBean("transferService"));
<!--引入cglib依赖包--> <dependency> <groupId>cglib</groupId> <artifactId>cglib</artifactId> <version>2.1_2</version> </dependency>