Spring框架学习——AOP的开发

一.AOP开发中的相关术语。html

  ——JoinPoint(链接点):指那些能够被拦截到的点。好比增删改查方法均可以加强,这些方法就能够被称为是链接点。java

  ——PointCut:切入点,真正被拦截的点,指对哪些链接点进行拦截的定义。JoinPoint是指方法能够加强,而切入点就是实际哪一个方法进行加强或修改,这样的方法被称为切入点。web

  ——Advice(加强/通知):方法层面的加强。指拦截到了方法后须要作的事情,也就是加强的功能部分被称为通知。分为前置(方法主体以前)、后置、环绕通知。 spring

  ——Introduction(引介):是一种特殊的通知,再不修改类代码的前提下进行类层面的加强。express

  ——Target:代理的目标对象,在AOP中也能够说是被加强的对象,如对UserDao加强,那么UserDao就是目标对象。app

  ——Weaving(织入):指将通知(Advice)应用到目标(Target)的过程。 也就是将加强应用到目标对象来建立新的代理对象的过程。Spring采用动态织入的方式。eclipse

  ——Proxy(代理):一个类被AOP织入加强后,就产生一个结果代理类。ide

  ——Aspect(切面):是多个切入点和多个通知(引介)的结合。在代理中可能有切面。性能

 

2、Spring使用AspectJ进行AOP开发(XML方式单元测试

  A.建立动态web项目,引入jar包。

    spring核心开发包。

    Spring的AOP开发包。spring-aop-4.2.4.RELEASE.jar         com.springsource.org.aopalliance-1.0.0.jar

    aspectJ的开发包:com.springsource.org.aspectj.weaver-1.6.8.RELEASE.jar           spring-aspects-4.2.4.RELEASE.jar

    

 

  B.配置文件(如今开发AOP,因此要引入AOP的xml规范)

  这些xml规范不用记,在spring-framework-4.2.4.RELEASE-dist\docs\spring-framework-reference\html\xsd-configuration.html中就能够找到各类约束。

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:aop="http://www.springframework.org/schema/aop" xsi:schemaLocation="
        http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd
        http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop.xsd"> <!-- bean definitions here -->


</beans>

 

   C.建立目标类进行配置  

 
 

  public interface OrderDao {

    void findAll();

    void remove();

    void save();

    void update();
  }

 
 

  public class OrderDaoImpl implements OrderDao {

    @Override
    public void findAll() {
      System.out.println("查找全部订单......");
    }

    @Override
    public void remove() {
      System.out.println("移除订单......");
    }

    @Override
    public void save() {
      System.out.println("保存客户订单......");
    }

    @Override
    public void update() {
      System.out.println("修改订单信息......");
    }

}

 
<!-- 对目标类进行代理,交给spring管理 -->
    <bean id="orderDao" class="cn.xxx.spring4.demo1.OrderDaoImpl"></bean>

 

 D.编写测试类。

  

//Spring与Junit整合的jar,用来单元测试,在别的地方也能够用到,可是其余地方须要开启spring注解才能用,contextConfiguration是用来加载配置文件
@RunWith(SpringJUnit4ClassRunner.class)
@ContextConfiguration("classpath:/config/applicationContext1.xml")
public class demo1 {
    
//    为属性设置值
    @Resource(name="orderDao")
    private OrderDao orderDao;
    
    @Test
    public void test1() {
        orderDao.findAll();
    }
}

测试结果:

18:04:16,743  INFO DefaultTestContextBootstrapper:259 - Loaded default TestExecutionListener class names from location [META-INF/spring.factories]: [org.springframework.test.context.web.ServletTestExecutionListener, org.springframework.test.context.support.DirtiesContextBeforeModesTestExecutionListener, org.springframework.test.context.support.DependencyInjectionTestExecutionListener, org.springframework.test.context.support.DirtiesContextTestExecutionListener, org.springframework.test.context.transaction.TransactionalTestExecutionListener, org.springframework.test.context.jdbc.SqlScriptsTestExecutionListener]
18:04:16,747  INFO DefaultTestContextBootstrapper:207 - Could not instantiate TestExecutionListener [org.springframework.test.context.transaction.TransactionalTestExecutionListener]. Specify custom listener classes or make the default listener classes (and their required dependencies) available. Offending class: [org/springframework/transaction/interceptor/TransactionAttributeSource]
18:04:16,749  INFO DefaultTestContextBootstrapper:207 - Could not instantiate TestExecutionListener [org.springframework.test.context.web.ServletTestExecutionListener]. Specify custom listener classes or make the default listener classes (and their required dependencies) available. Offending class: [org/springframework/web/context/request/RequestAttributes]
18:04:16,750  INFO DefaultTestContextBootstrapper:207 - Could not instantiate TestExecutionListener [org.springframework.test.context.jdbc.SqlScriptsTestExecutionListener]. Specify custom listener classes or make the default listener classes (and their required dependencies) available. Offending class: [org/springframework/transaction/interceptor/TransactionAttribute]
18:04:16,751  INFO DefaultTestContextBootstrapper:185 - Using TestExecutionListeners: [org.springframework.test.context.support.DirtiesContextBeforeModesTestExecutionListener@13c78c0b, org.springframework.test.context.support.DependencyInjectionTestExecutionListener@12843fce, org.springframework.test.context.support.DirtiesContextTestExecutionListener@3dd3bcd]
18:04:16,814  INFO XmlBeanDefinitionReader:317 - Loading XML bean definitions from class path resource [config/applicationContext1.xml]
18:04:16,881  INFO GenericApplicationContext:578 - Refreshing org.springframework.context.support.GenericApplicationContext@59fa1d9b: startup date [Fri May 10 18:04:16 CST 2019]; root of context hierarchy
查找全部订单......
18:04:16,940  INFO GenericApplicationContext:960 - Closing org.springframework.context.support.GenericApplicationContext@59fa1d9b: startup date [Fri May 10 18:04:16 CST 2019]; root of context hierarchy

 

E.通知类型

  前置通知 :在目标方法执行以前执行.

  后置通知 :在目标方法执行以后执行

  环绕通知 :在目标方法执行前和执行后执行

  异常抛出通知:在目标方法执行出现异常的时候执行

  最终通知 :不管目标方法是否出现异常最终通知都会执行.至关于final

演示:建立一个切面类(指的是该类能够横向切入一个链接点),好比权限校验方法。在建立以前咱们先了解一下切入点表达式,所谓切入点表达式经过一些特色的表达式,Spring底层经过反射来将切入的点(具体要加强的方法)的全路径+方法名与表达式一一对应、

  切入点表达式:execution(表达式) 

    表达式意义:      []表明能够省略 ,因为方法参数通常不知道,因此用..表示  execution表明执行

    [方法访问修饰符] 方法返回值 包名.类名.方法名(方法的参数) 

    public * cn.itcast.spring.dao.*.*(..)   * 表明任意的意思,这里表明方法返回值为全部,类名和方法名任意,也就是找cn.itcast.spring.dao包下面的全部类中的方法,都被加强
  * cn.itcast.spring.dao.*.*(..) 
  * cn.itcast.spring.dao.UserDao+.*(..) 当前UserDao类及其子类的全部方法
  * cn.itcast.spring.dao..*.*(..) 当前包及其子包下的类的全部方法

切面类:

 
 

public class MyAspect {
  public void validate() {
    System.out.println("权限校验");
  }

  public void logWrite(Object result) {
    System.out.println("日志记录");
  }
}

 

前置通知 

<!--配置 -->
<!-- 对目标类进行代理,交给spring管理 -->
    <bean id="orderDao" class="cn.xxx.spring4.demo1.OrderDaoImpl"></bean>
    <bean id="myAspect" class="cn.xxx.spring4.demo1.MyAspect"></bean>
    
    <aop:config>
        <aop:pointcut expression="execution (* cn.xxx.spring4.demo1.OrderDaoImpl.findAll(..))" id="pointcut1"/>
        <aop:aspect ref="myAspect">
       <!-- 前置通知 --> <aop:before method="validate" pointcut-ref="pointcut1"/> </aop:aspect> </aop:config>

运行结果:

权限校验
查找全部订单......

后置通知

<aop:pointcut expression="execution(* cn.xxx.spring4.demo1.OrderDaoImpl.remove(..))" id="pointcut2"/>

    <!-- 后置通知,这里面returning的返回值和切面类中的切入点方法里面的参数一致就行, -->    
            <aop:after-returning method="logWrite" pointcut-ref="pointcut2" returning="result"/>

运行结果:

移除订单......
日志记录

 

环绕通知

切面类方法:

public void check(ProceedingJoinPoint joinPoint) throws Throwable {
        System.out.println("开启性能监控");
//        执行切入点的目标程序,在方法先后插入,那么中间的本来方法必定要执行,这句话就是执行原有方法的代码
        joinPoint.proceed();
        System.out.println("结束性能监控");
    }

配置:

<aop:pointcut expression="execution(* cn.xxx.spring4.demo1.OrderDaoImpl.update(..))" id="pointcut3"/>

<aop:aspect ref="myAspect">
        <!-- 环绕通知 -->
            <aop:around method="check" pointcut-ref="pointcut3"/>
        </aop:aspect>

运行结果:

开启性能监控
修改订单信息......
结束性能监控

异常抛出通知

  切面类方法:

方法参数为Throwable ex,异常对象,和配置中保持一致
public
void afterThrowing(Throwable ex) { ex.printStackTrace();
     system.out.println("发生除0异常") }

配置:

<!-- 异常抛出通知,注意这里的throwing属性的值必定和切面类方法里面的参数一致 -->
            <aop:after-throwing method="afterThrowing" pointcut-ref="pointcut4" throwing="ex"/>
        </aop:aspect>

若是切入点方法里面出现异常,通知就会生效,就会执行通知的方法。

通知方法(切面类的方法)

public void afterThrowing(Throwable ex) {
        ex.printStackTrace();
        System.out.println("发生除0异常");
    }

 

运行结果:

java.lang.ArithmeticException: / by zero
    at cn.xxx.spring4.demo1.OrderDaoImpl.save(OrderDaoImpl.java:20)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:302)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
    at org.springframework.aop.aspectj.AspectJAfterThrowingAdvice.invoke(AspectJAfterThrowingAdvice.java:58)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
    at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
    at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:208)
    at com.sun.proxy.$Proxy13.save(Unknown Source)
    at cn.xxx.test.demo1.testSave(demo1.java:41)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
    at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
    at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
    at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
    at org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:75)
    at org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:86)
    at org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:84)
    at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
    at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:254)
    at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:89)
    at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
    at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
    at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
    at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
    at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
    at org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)
    at org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:70)
    at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
    at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:193)
    at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:89)
    at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:41)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:541)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:763)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:463)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:209)
发生除0异常

最终通知:和上面相似就不演示了。

相关文章
相关标签/搜索