spring 测试层学习记录

springmvc web层测试

Author : Janloong Do_O

基础依赖

test依赖

<dependency>
    <groupId>junit</groupId>
    <artifactId>junit</artifactId>
    <version>${junit.version}</version>
    <scope>test</scope>
</dependency>

org.hamcrest
hamcrest-core
1.3
test

<dependency>
    <groupId>org.mockito</groupId>
    <artifactId>mockito-core</artifactId>
    <version>2.10.0</version>
    <scope>test</scope>
</dependency>


<dependency>
    <groupId>org.springframework</groupId>
    <artifactId>spring-test</artifactId>
    <version>${spring.version}</version>
    <scope>test</scope>
</dependency>

spring拦截器

spring 的三种拦截器

近似总拦截器，拦截所有url
<mvc:interceptors>
    <bean class="com.app.mvc.MyInteceptor" />
</mvc:interceptors>

近似总拦截器，拦截匹配的url
<mvc:interceptors >
  <mvc:interceptor>
        <mvc:mapping path="/user/*" /> <!-- /user/*  -->
        <bean class="com.mvc.MyInteceptor"></bean>
    </mvc:interceptor>
</mvc:interceptors>

如果是REST风格的URL，静态资源就不会被拦截。因为我们精准的注入了拦截器
<bean class="org.springframework.web.servlet.mvc.annotation.DefaultAnnotationHandlerMapping">
 <property name="interceptors">
     <list>
         <bean class="com.mvc.MyInteceptor"></bean>
     </list>
 </property>
</bean>

自动注册DefaultAnnotationHandlerMapping 与AnnotationMethodHandlerAdapter 这两个bean,所以就没有机会再给它注入interceptors属性，就无法指定拦截器

事务回滚

<!-- 将数据源映射到sqlsessionfactory中 -->
<bean id="mybatisSqlSessionFactory" class="org.mybatis.spring.SqlSessionFactoryBean">
    <property name="dataSource" ref="dataSource"/>
    <property name="configLocation" value="classpath:/mybatis/mybatis-config.xml"/>
    <!--启动扫描mapper.xml文件-->
    <property name="mapperLocations">
        <list>
            <value>classpath:/mybatis/mapper/*Dao.xml</value>
        </list>
    </property>
</bean>

<!--将会查找类路径下的映射器并自动将它们创建成MapperFactoryBean-->
<bean class="org.mybatis.spring.mapper.MapperScannerConfigurer">
    <property name="basePackage" value="com.janloong.dao"/>
    <property name="sqlSessionFactoryBeanName" value="mybatisSqlSessionFactory"/>
</bean>

<!-- (事务管理器)transaction manager, use JtaTransactionManager for global tx -->
<bean id="transactionManager" class="org.springframework.jdbc.datasource.DataSourceTransactionManager">
    <property name="dataSource" ref="dataSource"/>
</bean>

<!--声明式事务，支持 @Transactional 标记-->
<tx:annotation-driven/>
<tx:advice id="txAdvice" transaction-manager="transactionManager">
    <tx:attributes>
        <tx:method name="get*" propagation="REQUIRED" read-only="true"/>
        <tx:method name="find*" propagation="REQUIRED" read-only="true"/>
        <tx:method name="load*" propagation="REQUIRED" read-only="true"/>
        <tx:method name="search*" propagation="REQUIRED" read-only="true"/>
        <tx:method name="query*" propagation="REQUIRED" read-only="true"/>
        <tx:method name="datagrid*" propagation="REQUIRED" read-only="true"/>

        <tx:method name="save*" propagation="REQUIRED"/>
        <tx:method name="add*" propagation="REQUIRED"/>
        <tx:method name="update*" propagation="REQUIRED"/>
        <tx:method name="delete*" propagation="REQUIRED"/>
        <tx:method name="create*" propagation="REQUIRED"/>
        <tx:method name="*" propagation="SUPPORTS"/>
    </tx:attributes>
</tx:advice>

<aop:config proxy-target-class="true">
    <!--只对业务逻辑层进行事务控制-->
    <aop:pointcut id="interceptorPointCuts"
                  expression="execution(* com.janloong.service.impl.*Impl.*(..))"/>
    <!--advisor定义，切入点和通知分别为interceptorPointCuts，txAdvice -->
    <aop:advisor advice-ref="txAdvice" pointcut-ref="interceptorPointCuts"/>
</aop:config>

大坑点

声明式事务回滚，容易遭成事务不生效的一个情况是
transactionManager 事务管理器在未注入前，已经注入过service层
导致 @transactional 注解不生效，从而导致事务回滚失效
根节点在于扫描包时,不应在application.xml(即web.xml中)扫描service,
但可以扫描controller，在其他xml中再去扫描service

应该在contxt xml 层不加载controller 但加载service
在mvc  xml 层加载controller