I was recently very surprised to find that jars in the JBOSS_DIST/lib are available on the classloader to WARS (jboss version 4.0.2). Specifically, dom4j.jar was the culprit in the issue we were tracking down. I have always worked under the assumption that only jars in jboss/server/default/lib were available. We jave the Java2ClassloaderCompliance set to false as well as false for the JBossWebLoader - purely a stock install. Is this behavior expected? My belief was supported in that you find commons.logging jar in both jboss/lib and jboss/server/default/lib. If jboss/lib is meant to be visible, why have it in both places? I made sure the class in dom4j.jar was not available anywhere else by running the following search with the output below:
[me@myserver ]$ find /usr/local/jboss -type f -name '*.jar' -print0 | xargs -n1 -0i sh -c 'jar tf "{}" | grep -q SAXReader && echo "{}"'
./lib/dom4j.jar
Any thoughts?
Thanks,
Brian
