MTP:[EMAIL PROTECTED]]
Sent: Wednesday, December 20, 2000 6:06 AM
To: Tomcat
Subject: sealing violation in 4.0m5
Trying to port my 3.2 app to 4.0. One simple page works, but the main
page
of my app yeilds the exception below. Any idea what a "sealing violation'
is? Sounds like a
,
Bill Pfeiffer
- Original Message -
From: "Kitching Simon" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, December 20, 2000 6:06 AM
Subject: RE: sealing violation in 4.0m5
Hi Bill.
I believe a "sealing violation" is when a class which was loaded under on
Bill Pfeiffer wrote:
Classpath is not set (ie set to empty) when starting Tomcat.
With Tomcat 4.0 using standard startup scripts, this does not matter --
the user's CLASSPATH variable is totally ignored.
My web app
does include some jars, none of which should clash with Tomcat.
My
