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 u
EB-INF/class
> directory.
>
> Thanks,
>
> Bill Pfeiffer
>
> - Original Message -
> From: "Kitching Simon" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, December 20, 2000 6:06 AM
> Subject: RE: sealing v
,
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
Hi Bill.
I believe a "sealing violation" is when a class which was loaded under one
classloader tries to call a class loaded under a different classloader, in
circumstances where this isn't allowed.
I suggest that the problem is therefore something to do with classpaths,
ie your classpath inclu
