ModuleClassLoader for WAR only sees WEB-INF/lib and WEB-INF/classes (no "resources") ?

[drh01]

I am debugging a classloading issue; my spring ContextLoaderListener is attempting to load an XML file from WEB-INF/beanRefContext.xml.

The appropriate ModuleClassLoader is being used (deployment.myapp.war:main), but a call to getResource("WEB-INF/beanRefContext.xml") (or other variations, classpath*:, etc.) always fail.

I drilled down into the ModuleClassLoader in the debugger, and it appears it only contains JARs from WEB-INF/lib and class files from WEB-INF/classes... in fact I can step and watch it search inside each JAR for that file.  But it doesn't search the top-level root WEB-INF directory.

Why can't this classloader load a resource from WEB-INF/ ?

Thanks.

[robby.cornelissen]

Which object are you calling getResource() on? The ServletContext?

[drh01]

getResource() is being called on the ModuleClassLoader, where the module is the war deployment.  (Note, I am not calling getResource directly, this is framework code that ends up calling it -- but in the debugger I have verified that it is the ModuleClassLoader for the war deployment being used).

[sfcoy]

WEB-INF is not part of the classpath. JBossAS/WildFly is behaving correctly.

In order for the Spring Framework to find your configuration files you must set the contextConfigLocation context-param in your web.xml file:

{code:xml}    <context-param>
        <param-name>contextConfigLocation</param-name>
        <param-value>/WEB-INF/beanRefContext.xml</param-value>
    </context-param>{code}

[drh01]

Thanks Stephen.  I didn't really suspect a JBoss bug here, I assumed it was misconfiguration or something I was just missing.

As an aside, contextConfigLocation doesn't come into play in my scenario; ContextListenerLoader also has an option to specify a parent context which is loaded through the classloader  -- this is what I was working with (presumably contextConfigLocation is loaded using ServletContext).

Thanks again for the clarification.

Stephen Coy wrote:

WEB-INF is not part of the classpath. JBossAS/WildFly is behaving correctly.

In order for the Spring Framework to find your configuration files you must set the contextConfigLocation context-param in your web.xml file:

    <context-param>
        <param-name>contextConfigLocation</param-name>
        <param-value>/WEB-INF/beanRefContext.xml</param-value>
    </context-param>