WEB-INF/classes/ vs WEB-INF/lib/*.jar in classpath priority?

Question

a war packaged for a tomcat webapp contains WEB-INF/classes and WEB-INF/lib/*.jar

which of them has higher priority in the CLASSPATH?

the reason I'm asking is, that my application uses A.jar, which contains aspects generated from an aspectj project; and B.jar, which are to be woven with the aspects from A.jar. when the project myapp is compiled, it generates many Classes which override those same classes from B.jar, these are packaged into the WEB-INF/classes dir. so if tomcat load WEB-INF/lib/*.jar first, then the woven aspects won't take effect

ziggy ziggy · Accepted Answer · 2011-12-04T13:33:31

When a request to load a class from the web application's WebappX class loader is processed, this class loader will look in the local repositories first, instead of delegating before looking. There are exceptions. Classes which are part of the JRE base classes cannot be overriden. For some classes (such as the XML parser components in J2SE 1.4+), the J2SE 1.4 endorsed feature can be used (see the common classloader definition above). Last, any JAR containing servlet API classes will be ignored by the classloader. All other class loaders in Tomcat 5 follow the usual delegation pattern.

Therefore, from the perspective of a web application, class or resource loading looks in the following repositories, in this order:

Bootstrap classes of your JVM
System class loader classes (described above)
/WEB-INF/classes of your web application
/WEB-INF/lib/*.jar of your web application
$CATALINA_HOME/common/classes
$CATALINA_HOME/common/endorsed/*.jar
$CATALINA_HOME/common/i18n/*.jar
$CATALINA_HOME/common/lib/*.jar
$CATALINA_BASE/shared/classes
$CATALINA_BASE/shared/lib/*.jar

So WEB-INF/classes is searched first before WEB-INF/lib

Ref: http://tomcat.apache.org/tomcat-5.5-doc/class-loader-howto.html

WEB-INF/classes/ vs WEB-INF/lib/*.jar in classpath priority?

2 Answers