sealing violation is new in jdk 1.3 and addresses a potential security problem. The
java web site has notes on this.
What I found is that certain xml related jar files each includes the class files for
dom, sax, jaxp etc.
You can mess with the order of the jar files on your class path to work around the
problem.
I put together a small util to check package definition conflicts and found that
xerces.jar (and likely xalan.jar), crimson.jar and
saxon.jar all, for convenience, include some each of the dom, sax and jaxp packages.
HTH
> Date: Thu, 24 May 2001 13:50:06 -0500
> To: [EMAIL PROTECTED]
> From: Aristide Aragon <[EMAIL PROTECTED]>
> Subject: FATAL: configuration error
> Message-ID: <[EMAIL PROTECTED]>
>
> Hello
>
> When I start tomcat, by typing $TOMCAT_HOME/bin/startup.sh I
> get the classpath printed, and then:
>
> FATAL: configuration error
> java.lang.SecurityException: sealing violation
> at
> java.net.URLClassLoader.defineClass(URLClassLoader.java:234)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:297)
> at
> sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:286)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:253)
> at
> java.lang.ClassLoader.loadClassInternal(ClassLoader.java:313)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:120)
> at
> javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactor
> y.java:117)
> at
> org.apache.tomcat.util.xml.XmlMapper.readXml(XmlMapper.java:210)
> at org.apache.tomcat.startup.Tomcat.execute(Tomcat.java:187)
> at org.apache.tomcat.startup.Tomcat.main(Tomcat.java:235)
>
> What could that be? This is a fresh install
>
> Aristide
