On Thu, 31 Jan 2002, Paul Worrall wrote:
> Date: Thu, 31 Jan 2002 11:47:15 -0000
> From: Paul Worrall <[EMAIL PROTECTED]>
> Reply-To: Tomcat Users List <[EMAIL PROTECTED]>,
> [EMAIL PROTECTED]
> To: Tomcat Users List <[EMAIL PROTECTED]>
> Subject: RE: JAXB and Tomcat Problem
>
> Yes, and I have just found that it works under the j2sdkee1.3 which is
> Apache Tomcat/4.0-b4-dev so I must be going wrong somewhere.
>
> Any idea what the "java.lang.SecurityException: sealing violation" might
> mean ? That might help me reach some conclusions.
>
> Thanks Oliver.
A "sealing violation" exception happens in the following scenario:
* You have multiple classes in a given Java package.
* These multiple classes are loaded from different JAR files.
* At least one of the JAR files has the "sealed" attribute set
in it's "META-INF/MANIFEST.MF" file.
The only JAR files I *know* that are sealed are jaxp.jar and crimson.jar
in the JAXP/1.1 release -- they definitely cause grief for lots of people
who try to put a parser in their own WEB-INF without removing the global
one Tomcat provides to everyone. Sorry, I don't know how JAXB works in
this respect.
Craig
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>
