[
https://issues.apache.org/jira/browse/WW-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12910360#action_12910360
]
Ty Connell commented on WW-3443:
--------------------------------
I was able to overcome this by overriding the protected method
setupBeforeInitDispatcher like so:
@Override
protected void setupBeforeInitDispatcher() throws Exception {
String[] contextLocations = new String[]{
"classpath:applicationContext-security.xml",
"classpath:applicationContext.xml",
"classpath:junitApplicationContext.xml" };
GenericXmlContextLoader xmlContextLoader = new
GenericXmlContextLoader();
applicationContext = xmlContextLoader.loadContext(contextLocations);
servletContext.setAttribute(WebApplicationContext.ROOT_WEB_APPLICATION_CONTEXT_ATTRIBUTE,
applicationContext);
}
> StrutsSpringTestCase does not support multiple spring xml configuration files
> -----------------------------------------------------------------------------
>
> Key: WW-3443
> URL: https://issues.apache.org/jira/browse/WW-3443
> Project: Struts 2
> Issue Type: Bug
> Affects Versions: 2.1.8.1
> Reporter: Paul Grove
>
> Spring has a great concept that you can load the xml configuration and define
> beans with the same name multiple times and the convention is that the lasr
> definition takes precedence. This is great for testing as we usually load the
> normal (production) application context xml then load a test application
> context xml which just overides the beans that need to be changed for that
> test.
> Currently the StrutsSpringTestCase does not support defining multiple
> application context xml files for a test. I rewrote the class so that the
> method protected String getContextLocations() is now protected String[]
> getContextLocations(). We can now load multiple application context xml files.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
