仍是接着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>