2

我正在尝试使用 XML 配置和带@Configuration注释的类的组合来配置 Spring MVC 集成测试。

@RunWith(SpringJUnit4ClassRunner.class)
@WebAppConfiguration
@TestPropertySource({"/spring-security.properties",
                     "/rabbitmq-default.properties",
                     "/mongodb-default.properties",
                     "/webapp-override.properties"})
@ContextHierarchy({
    @ContextConfiguration("classpath:**/security-config.xml"),
    @ContextConfiguration(classes = RootConfig.class),
    @ContextConfiguration(classes = SpringMvcConfig.class)
})
public class BaseConfiguredMvcIntegrationTest {
}

java配置已正确初始化。问题是尽管"**/security-config.xml"在初始化期间找到并解析了该文件......其中定义的所有 Spring 安全 bean 从未在WebApplicationContext.

Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type [org.springframework.security.crypto.bcrypt.BCryptPasswordEncoder] found for dependency: expected at least 1 bean which qualifies as autowire candidate for this dependency. Dependency annotations: {@org.springframework.beans.factory.annotation.Autowired(required=true)}
    at org.springframework.beans.factory.support.DefaultListableBeanFactory.raiseNoSuchBeanDefinitionException(DefaultListableBeanFactory.java:1301)
    at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1047)
    at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:942)
    at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:533)

所以我的问题是如何在 Spring MVC 集成测试中同时使用基于 XML 和基于注释的配置？

我可以将 spring 安全配置更改为基于 java/annotated 的配置...我宁愿不这样做。我发现使用 spring 安全命名空间比使用 java 配置更具可读性和简洁性。

另外，请注意这种组合的 XML/Java 配置在非测试环境中工作得非常好。

  • 春天 v4.1.6
  • Spring Security v4.0.1

WebApplicationContext 配置：

package com.gggdw.web.config;

import javax.servlet.FilterRegistration;
import javax.servlet.ServletContext;
import javax.servlet.ServletException;
import javax.servlet.ServletRegistration;

import org.springframework.context.annotation.Configuration;
import org.springframework.web.WebApplicationInitializer;
import org.springframework.web.context.ContextLoaderListener;
import org.springframework.web.context.support.AnnotationConfigWebApplicationContext;
import org.springframework.web.filter.DelegatingFilterProxy;
import org.springframework.web.filter.HiddenHttpMethodFilter;
import org.springframework.web.servlet.DispatcherServlet;


@Configuration
public class GGGWebInitializer implements WebApplicationInitializer {

    public static final String SERVLET_NAME = "ggg";

    @Override
    public void onStartup(ServletContext servletContext) throws ServletException {
        // Create the 'root' Spring application context
        AnnotationConfigWebApplicationContext rootContext = new AnnotationConfigWebApplicationContext();
        rootContext.register(RootConfig.class);

        // Manage the lifecycle of the root application context
        servletContext.addListener(new ContextLoaderListener(rootContext));

        // Create the dispatcher servlet's Spring application context
        AnnotationConfigWebApplicationContext dispatcherContext = new AnnotationConfigWebApplicationContext();
        dispatcherContext.register(SpringMvcConfig.class);

        // Register and map the dispatcher servlet
        ServletRegistration.Dynamic dispatcher = servletContext.addServlet(SERVLET_NAME, new DispatcherServlet(dispatcherContext));
        dispatcher.setLoadOnStartup(1);
        dispatcher.addMapping("/");

        //Spring security config
        FilterRegistration.Dynamic springSecurityFilterChain = servletContext.addFilter(
                                                    "securityFilter", new DelegatingFilterProxy("springSecurityFilterChain"));

        springSecurityFilterChain.addMappingForServletNames(null, false, SERVLET_NAME);
        //springSecurityFilterChain.setAsyncSupported(true);

        servletContext.addFilter("hiddenHttpMethodFilter", HiddenHttpMethodFilter.class);

    }

}

RootConfig.class

@Configuration
@Import({WebPropertiesConfig.class,                     // loads all properties files on class path from resources folder
         MongoConfig.class                              // init mongodb connection 
         })                     
@ImportResource({"classpath:**/security-config.xml"})   // spring security xml config (java config not as readable)
public class RootConfig {

}

安全配置.xml

<?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:security="http://www.springframework.org/schema/security"
       xmlns:context="http://www.springframework.org/schema/context"
       xsi:schemaLocation="
           http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd
           http://www.springframework.org/schema/security http://www.springframework.org/schema/security/spring-security.xsd
           http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context.xsd">

    <!-- <context:property-placeholder location="classpath:spring-security.properties" /> -->

    <security:global-method-security pre-post-annotations="enabled" secured-annotations="enabled">
       <security:expression-handler ref="expressionHandler"/>
    </security:global-method-security>

    <bean id="expressionHandler" class="org.springframework.security.access.expression.method.DefaultMethodSecurityExpressionHandler">
        <property name="permissionEvaluator" ref="permissionEvaluator"/>
    </bean>

    <bean id="permissionEvaluator"
          class="com.my.local.package.security.GenericPermissionEvaluator">
    </bean>

    <!-- Configure Spring Security -->
    <security:http auto-config="true" use-expressions="true" >
        <security:form-login login-page="${spring.security.login-page}" 
                             login-processing-url="${spring.security.login-processing-url}" 
                             default-target-url="${spring.security.default-target-url}" 
                             authentication-failure-url="${spring.security.authentication-failure-url}" 
                             username-parameter="${spring.security.username-parameter}"
                             password-parameter="${spring.security.password-parameter}"
        />
        <security:logout logout-url="${spring.security.logout-url}" 
                 logout-success-url="${spring.security.logout-success-url}" />

        <security:intercept-url pattern="/**" requires-channel="https" />
        <security:intercept-url pattern="/s/**" access="isAuthenticated()" requires-channel="https" />
        <security:custom-filter ref="log4JMDCFilter" after="SECURITY_CONTEXT_FILTER"/>
        <security:access-denied-handler error-page="${spring.security.access-denied-handler-error-page}" />
        <!-- <security:session-management invalid-session-url="${spring.security.invalid-session-url}"/> 
              2 types of invalid session, brand new user and a timeout of a previous logged in user
              both need to be handled differently -->
    </security:http>

    <bean id="customUserDetailsService" class="com.my.local.package.CustomUserDetailsService" depends-on="userRepository"/>   

    <bean id="bCryptPasswordEncoder" class="org.springframework.security.crypto.bcrypt.BCryptPasswordEncoder" />


   <!--  log4j filter to add userName and ipAddress into logging on a per request/thread basis -->
    <bean id="log4JMDCFilter" class="com.my.local.package.filter.Log4JMDCFilter"/>

    <security:authentication-manager>
       <security:authentication-provider user-service-ref="customUserDetailsService">
           <security:password-encoder ref="bCryptPasswordEncoder"/>
       </security:authentication-provider>
    </security:authentication-manager>


</beans>
4

2 回答 2

0

更新：经过进一步考虑并根据您的最新反馈，您遇到的行为可能是 Spring Framework 4.1.4 中引入的错误的结果（有关详细信息，请参阅SPR-13075）。

尝试降级到 Spring Framework 4.1.3，如果您仍然遇到不良行为，请告诉我。

请注意，这种组合的 XML/Java 配置在非测试环境中工作得非常好。

怎么会这样？

您是否确实在生产中的层次结构中加载了三 (3) 个上下文？

我不信。相反，我假设您以某种方式从and加载单个根 。WebApplicationContext"classpath:**/security-config.xml"RootConfig.class

因此，最重要的问题是：您如何在生产环境中配置根 WebApplicationContext？

一旦你回答了这个问题，我就可以告诉你如何在你的测试配置中实现同样的目标。;)

问候，

Sam（Spring TestContext 框架的作者）

于 2015-06-03T16:03:04.727 回答
0

注意来自PathMatchingResourcePatternResolver的注释：

请注意，当与 Ant 样式模式结合使用时，“classpath*:”只能在模式开始前至少在一个根目录下可靠地工作，除非实际的目标文件驻留在文件系统中。这意味着像 "classpath*:*.xml" 这样的模式不会从 jar 文件的根目录中检索文件，而只会从扩展目录的根目录中检索文件。这源于 JDK 的 ClassLoader.getResources() 方法的限制，该方法仅返回传入的空字符串的文件系统位置（指示要搜索的潜在根）。

于 2015-12-02T22:18:30.900 回答