as far as I know it means that you have a class name collision in two jars
and one of them is sealed, I had a similar problem when using xml packages.
Try to put jars foreign to tomcat in the begining of the classpath, or at
the end... classpath reordering did it for me..
--V.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 13, 2001 11:46 AM
To: [EMAIL PROTECTED]
Subject: java.lang.SecurityException: sealing violation?
Okay, I gave up on my tomcat installation. I wiped
everything clean and then got all the source in the
hopes that it might work better if I compiled
vs. dropping binaries.
So, there are many confusing aspects of the
installation instructions regarding building the
source. Seems like maybe the docs don't match up with
the behavior of the current releases?
Anyway, I plodded thru, I think I got everything
straight. BUT, when I run startup.sh, I get the
following:
java.lang.SecurityException: sealing violation
I followed the install instructions that came with the
JSSE from Sun. Have no idea what this error means.
Can anyone help?
Thanks.
- Jeremy
***********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. Any unauthorized review, use, disclosure or distribution
is prohibited. If you are not the intended recipient, please contact
the sender by reply e-mail and destroy all copies of the original
message.
***********************************************************************
