Hi Chuck,
Thank you very much for your feedback. Your comments about reflection
were right on the money and have helped me resolve the underlying issue.
It turns out that my initial assertion about our server/lib classes
being visible to our web app was incorrect -- it was just that our
custom
Thank you for your quick reply. I think I understand the distinction you
make between a class being available and a class being loaded, although
it is a bit confusing. I suspect that if I understand this clearly, it
will help me track down the cause of my problem.
Given the Tomcat ClassLoader
From: Gary Hirschhorn [mailto:[EMAIL PROTECTED]
Subject: RE: Classes in tomcat\server\lib folder sometimes
are visible to web application
The Catalina ClassLoader in server/lib creates Webapp1 ClassLoader
specifically for webapp1.
It's actually org.apache.catalina.loader.WebappLoader that
From: Gary Hirschhorn [mailto:[EMAIL PROTECTED]
Subject: Classes in tomcat\server\lib folder sometimes are
visible to web application
According to this documentation, classes in this jar
should be TOTALLY invisible to web applications.
That's not quite the case. Classes outside of a given
