带有弹簧集成的Struts 2.5 Junit测试设置

如何解决带有弹簧集成的Struts 2.5 Junit测试设置

支柱版本：2.5.25

春季版：4.3.26

使用：struts2-rest-plugin，struts2-spring-plugin，JUnit 4

我正在寻求帮助来纠正我的单元测试配置，该配置当前抛出异常“ ServletContext不能为空”。下面是堆栈跟踪：

Unable to instantiate Action,com.hs.iws.actions.security.LoginAction,defined for 'login' in namespace '/security'Error creating bean with name 'com.hs.iws.actions.security.LoginAction': Invocation of init method Failed; nested exception is java.lang.IllegalArgumentException: ServletContext must not be null
    at com.opensymphony.xwork2.DefaultActionInvocation.createAction(DefaultActionInvocation.java:320)
    at com.opensymphony.xwork2.DefaultActionInvocation.init(DefaultActionInvocation.java:401)
    at com.opensymphony.xwork2.DefaultActionProxy.prepare(DefaultActionProxy.java:201)
    at com.opensymphony.xwork2.DefaultActionProxyFactory.createActionProxy(DefaultActionProxyFactory.java:76)
    at org.apache.struts2.rest.RestActionProxyFactory.createActionProxy(RestActionProxyFactory.java:50)
    at org.apache.struts2.StrutsJUnit4TestCase.getActionProxy(StrutsJUnit4TestCase.java:156)
    at com.hs.iws.actions.security.LoginActionTest.testValidation(LoginActionTest.java:41)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    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.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
    at org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:75)
    at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
    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:252)
    at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runchild(SpringJUnit4ClassRunner.java:94)
    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:191)
    at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
    at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
    at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
    at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
    at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
    at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
    at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.hs.iws.actions.security.LoginAction': Invocation of init method Failed; nested exception is java.lang.IllegalArgumentException: ServletContext must not be null
    at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProcessor.java:137)
    at org.springframework.beans.factory.support.AbstractAutowireCapablebeanfactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapablebeanfactory.java:407)
    at org.springframework.beans.factory.support.AbstractAutowireCapablebeanfactory.initializeBean(AbstractAutowireCapablebeanfactory.java:1611)
    at org.springframework.beans.factory.support.AbstractAutowireCapablebeanfactory.initializeBean(AbstractAutowireCapablebeanfactory.java:398)
    at com.opensymphony.xwork2.spring.SpringObjectFactory.buildBean(SpringObjectFactory.java:201)
    at com.opensymphony.xwork2.spring.SpringObjectFactory.buildBean(SpringObjectFactory.java:169)
    at com.opensymphony.xwork2.ObjectFactory.buildBean(ObjectFactory.java:177)
    at com.opensymphony.xwork2.factory.DefaultActionFactory.buildAction(DefaultActionFactory.java:40)
    at com.opensymphony.xwork2.ObjectFactory.buildAction(ObjectFactory.java:142)
    at com.opensymphony.xwork2.DefaultActionInvocation.createAction(DefaultActionInvocation.java:301)
    ... 43 more
Caused by: java.lang.IllegalArgumentException: ServletContext must not be null
    at org.springframework.util.Assert.notNull(Assert.java:134)
    at org.springframework.web.context.support.WebApplicationContextUtils.getWebApplicationContext(WebApplicationContextUtils.java:108)
    at org.springframework.web.context.support.WebApplicationContextUtils.getWebApplicationContext(WebApplicationContextUtils.java:98)
    at com.hs.iws.actions.IwsActionSupport.getSpringContext(IwsActionSupport.java:166)
    at com.hs.iws.actions.IwsActionSupport.setupActionSupport(IwsActionSupport.java:112)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleElement.invoke(InitDestroyAnnotationBeanPostProcessor.java:366)
    at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleMetadata.invokeInitMethods(InitDestroyAnnotationBeanPostProcessor.java:311)
    at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProcessor.java:134)
    ... 52 more

单元测试（spring bean是通过注释配置的，我们没有使用任何xml）

@RunWith(SpringJUnit4ClassRunner.class)
@ContextConfiguration(classes = LoginActionspringConfig.class)
public class LoginActionTest extends IwsstrutsspringTestCase<LoginAction> {
    
    // THIS TEST RUNS OKAY
    @Test
    public void getActionMapping() {
        ActionMapping mapping = getActionMapping("/security/login");
        Assert.assertNotNull(mapping);
        Assert.assertEquals("/security",mapping.getNamespace());
        Assert.assertEquals("login",mapping.getName());
    }


    // THIS TEST PRODUCES THE ERROR WHEN CALLING getActionProxy()
    @Test
    public void testValidation() {
        
        // the login uses the create() which expects the POST method
        request.setMethod("POST");

        ActionProxy proxy = getActionProxy("/security/login");
        Assert.assertNotNull(proxy);

        LoginAction action = (LoginAction)proxy.getAction();
        Assert.assertNotNull(action);

        Assert.assertTrue("expected some field errors",!action.getFieldErrors().isEmpty());
    }
}

LoginActionspringConfig.class

@Configuration
public class LoginActionspringConfig {

    @Bean
    public IIwsAuthenticationService authenticationService() {
        return new IwsAuthenticationServicetest();
    }

    @Bean
    public ISecurityLogDao securityLogDao() {
        return new SecurityLogDaotest();
    }

    @Bean
    public IUsersDepartmentDao usersDepartmentDao() {
        return new UsersDepartmentDaotest();
    }

    @Bean
    public IDepartmentDao departmentDao() {
        return new DepartmentDaotest();
    }

    @Bean
    public IwsCookieInterface iwsCookie() {
        return new IwsCookietest();
    }

}

我的Web应用程序当前在web.xml中使用org.springframework.web.context.ContextLoaderListener

<listener>
        <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
    </listener>

，然后指定此contextClass

<context-param>
        <param-name>contextClass</param-name>
        <param-value>
            org.springframework.web.context.support.AnnotationConfigWebApplicationContext
        </param-value>
    </context-param>

我不确定，但是我怀疑我需要在单元测试配置中做一些额外的事情来解决这个问题。到目前为止，我一直找不到答案。

StrutsJUnit4TestCase中有一个servletContext字段，我已经确认它不是null。但是，我怀疑这只是为了满足撑杆而不是弹簧。通过Junit 4测试我的Struts动作时，有人可以帮我指出正确的方向来配置缺少的ServletContext吗？

更新11/1 下面是调试器的屏幕截图。我试图说的是，我相信在struts中有两个ServletContext，在春天中有一个。看起来Struts测试已在设置中填充了ServletContext。我的配置中是否缺少满足Spring空ServletContext的功能？

更新11/1 我已经弄清楚了错误是从哪里来的。正在测试的LoginAction继承了此方法，该方法在超类中被调用。

protected WebApplicationContext getSpringContext() {
        return WebApplicationContextUtils
                .getWebApplicationContext(ServletActionContext.getServletContext());
    }

ServletActionContext.getServletContext（）返回null，这是问题的原因。如何在单元测试中连接ServletActionContext以达到预期效果？

解决方法

我能够通过重写StrutsJunit4TestCase.getActionProxy（）解决此问题。我当前的动作设置是在构造动作时尝试访问WebApplicationContext，这是在当前getActionProxy（）将必要的对象注入ServletActionContext之前进行的。下面是我解决此问题的替代内容

    @Override
protected ActionProxy getActionProxy(String uri) {

    // the super.getActionProxy() already sets this,but does it at the end of the method.
    // the ActionProxy proxy = ... line is already expecting it to be present and produces a NPE
    ServletActionContext.setServletContext(servletContext);
    ServletActionContext.setRequest(request);
    ServletActionContext.setResponse(response);

    return super.getActionProxy(uri);
}