2

I have a web application, that contains a configuration xml file for one of my application services that is exposed as spring bean. Also I have a standalone java application(which references my web app project from its pom.xml) in the same workspace, that runs tests using Spring TestContext framework and one of the tests checks the configuration of that XML file.

However I have a problem with accessing this xml file from the standalone app:

Before setting-up the test, in my previous configuration, the file was accessed through ServletContext and was located in WEB-INF/ folder. However, to make it accessable from the test project I had to move it to source/ folder and load it with getClassLoader().getResourceAsStream() method instead that of ServletContext. But it makes editing the file cumbersome because every time the app has to be redeployed.

Is it possible to keep the file in WEB-INF/ folder but load it from the referencing project during the test-runs?

P.S. Currently it's an STS project with Tomcat server.

Boris Treukhov
  • 17,493
  • 9
  • 70
  • 91

4 Answers4

5

Definitely keep the file under WEB-INF/ folder if that's where it is supposed to live.

For your test classes that are being executed from the command line. Your can use getClassLoader().getResource() on a file that you know is in the root of your classpath (e.g. application.properties file). From there you know the structure of your project and where to find WEB-INF/ relative to the properties file. Since it returns a URL you can use it to figure out a path to the XML files you're looking for.

URL url = this.getClass().getClassLoader().getResource("application.properties");
System.out.println(url.getPath());

File file = new File(url.getFile());
System.out.println(file);

// now use the Files' path to obtain references to your WEB-INF folder

Hopefully you find this useful. I have had to make assumptions about how your test classes are runing etc.

Take a look at the File Class and it's getPath(), getAbsolutePath(), and getParent() methods that could be of use to you.

Brad
  • 15,186
  • 11
  • 60
  • 74
  • Thanks, I'll take that into account. However the problem is that in one case the file should be accessed via the ServletContext, but in other case via class loader(which may not work well on some application servers I suppose). So the problem is that I should switch between the method of resource loading in two cases(web and test-runs). – Boris Treukhov May 17 '12 at 16:53
  • Yes you're correct, because you have a web app it should use the standard ServletContext to access files in the WEB-INF folder. Then only implement this jiggery-pokery for your test code. – Brad May 17 '12 at 17:02
3

I ended up using Spring MockServletContext class and injecting it directly to my service bean, before the test runs, as my service implemented ServletContextAware : 

@RunWith(SpringJUnit4ClassRunner.class)
@ContextConfiguration(locations = { "/test-ctx.xml" } ) 
public class SomeServiceTest {

@Autowired
private MyServletContextAwareService myService;

@Before
public void before(){
            //notice that I had to use relative path because the file is not available in the test project
    MockServletContext mockServletContext = new MockServletContext("file:../<my web project name>/src/main/webapp"); 

    myService.setServletContext(mockServletContext);        
}

If I had several classes using Servlet Context, then the better solution would be to use WebApplicationContext instead the default one (currently provided by DelegatingSmartContextLoader), but it would require implementing custom ContextLoader class and passing its class name to @ContextConfiguration annotation.

alternative and somewhat cleaner solution which later came to my mind is to refactor the service and inject ServletContext via @Autowired instead of messing with ServletContextAware, and provide the bean of corresponding type(effectively a MockServletContext instance).

Possibly, in future the direct support of MockServletContext from test classes will be added to Spring see SPR-5399 and SPR-5243.

UPDATE FOR SPRING 3.2 In Spring 3.2 initialization of the servlet context became as simple as adding one @WebAppConfiguration annotation:

@RunWith(SpringJUnit4ClassRunner.class)
@WebAppConfiguration("file:../<my web project name>/src/main/webapp")
@ContextConfiguration(locations = { "/test-ctx.xml" } ) 
public class SomeServiceTest {

see details in the article

Boris Treukhov
  • 17,493
  • 9
  • 70
  • 91
3

In a Maven project I had same problem. I had no servletContext and couldn't access static file in WEB-INF directory. I came across to a solution by adding entry to pom.xml which gave me access to the directory. It actually includes this path to the classpath.

PS: I was using Tomcat container

<project>
    <build>
    <resources>
        <resource>
            <directory>src/main/webapp/WEB-INF</directory>
        </resource>
    </resources>
</project>
a.valchev
  • 388
  • 4
  • 10
1

It's a classpath resource, so put it on the classpath: $webapp/WEB-INF/classes

Maven projects will copy things in $module/src/main/resources to this location when packaging the webapp. (the former is a sourcepath, the latter - WEB-INF/classes - is always put on the classpath by the servlet container, per spec.)

ianpojman
  • 1,743
  • 1
  • 15
  • 20
  • It's already in the class path - now I need to move it back to the web content folder because the app needs to be redeployed every time the file changes which slows down the development. – Boris Treukhov May 19 '12 at 04:16
  • You might want to use the jetty plugin then and run your webapp 'unassembled'... that should help: http://wiki.eclipse.org/Jetty/Feature/Jetty_Maven_Plugin#jetty:run_:__Running_an_unassembled_webapp – ianpojman May 20 '12 at 02:19
  • +1 for the interesting jetty link, but now my tests run just fine without a webserver at all(by means of the Spring Test Context framework) – Boris Treukhov May 20 '12 at 16:38