It occurs to me that I didn't explain very well how this problem manifests
itself. The problem occurs when you have a tld inside a jar file. Here's
the scenario:
App 1:
1. Request for App1 comes into the server
2. Request is assigned to thread1.
3. App1 is loaded on thread1.
4. Request is proce
I'm running with Tomcat 4.1 and am seeing the following problem (and have
actually been seeing the problem since 4.0.4):
Jasper relies on the fact that the DirContext is bound in
DirContextURLStreamHandler based on the app classloader. This is bound when
the StandardContext is started, stopped,
