Kevin Ross wrote:
> I successfully started over again with a fresh installation of Tomcat
> 4.1.12-LE, uncovering another side effect of the tomcat classloader. I
> find that the ClassLoader-HOWTO is very vague in explaining the exact
> boundaries of the classloaders...here's why:
>
> To make
I successfully started over again with a fresh installation of Tomcat
4.1.12-LE, uncovering another side effect of the tomcat classloader. I
find that the ClassLoader-HOWTO is very vague in explaining the exact
boundaries of the classloaders...here's why:
To make it work:
moved commons-beanut
Environment:
commons-logging-1.0.2.jar
log4j-1.2.6.jar
Apache Tomcat/4.1.12-LE-jdk14
Situation:
I have my own realm implementation that is stable in Tomcat 4.0.3-LE,
and I'm moving up to 4.1.12. In addition, I am also moving all of my
codebase to the commons-logging package. After moving
