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,
in advance.
Richard
-Original Message-
From: Richard Frazer [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 24, 2002 12:18 PM
To: Tomcat-Dev (E-mail)
Subject: Help please: DirContextURLStreamHandler/Jasper question and
possi ble bug...
I'm running with Tomcat 4.1 and am seeing the following
-Original Message-
From: Richard Frazer [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 24, 2002 1:16 PM
To: 'Tomcat Developers List'
Subject: TLD's in jars don't work (was: RE: Help please:
DirContextURLStre amHandler/Jasper question and possible bug...)
It occurs to me that I didn't explain very
Hello,
I've been working lately on integrating Tomcat into our server. In order to
do so, we need to generate our own session ids. Therefore we need our own
Manager implementation.
Since we've got our own Manager, we'd like to assign that Manager to the
Engine or the Host instead of to each
