Hi all, class loader question (aren't they all?)
We're running against Weblogic, and Weblogic issues Service Packs which
inevitably are simply jar files with updated classes.
However, these jar files need to be specified BEFORE the regular weblogic
jar files in the classpath.
So, I'm curious as
Hello Will,
The way webapps work with classloaders is opposite that of the normal
classloader precedence. The WebappClassloader looks in its own
classloader for libraries first before looking at parent classloaders.
What normally happens is that the parent classloader is queried first
for
I had missed this. Thanks, Jacob.
At 01:14 PM 12/6/2002 -0600, you wrote:
Hello Will,
The way webapps work with classloaders is opposite that of the normal
classloader precedence. The WebappClassloader looks in its own
classloader for libraries first before looking at parent classloaders.
Hi,
Jacob's answer is right, but I don't know if it's a complete answer to
your question.
So, I'm curious as whether there is a determinate order that the files
in
WEB-INF/lib are placed on the classpath, and also whether lib is placed
before WEB-INF/classes. (i.e. is it alphabetical or simply
Jacob's answer is not strictly true: the order is only partially inverted.
The actual order is:
WEB-INF/classes
WEB-INF/lib/*.jar
System Loader (including $CATALINA_HOME/common/endorsed/*.jar)
$CATALINA_HOME/common/classes
$CATALINA_HOME/common/lib/*.jar
$CATALINA_HOME/shared/classes
