🚀 go-pugleaf

There is an older jaxp.jar and parser.jar (1.0) in your path.  Replace them
with your new version of jaxp

-Dan

"Hans Georg Frey" <HGFrey@t-online.de> wrote in message
news:3BF2BCE6.83883153@t-online.de...
> Hi,
>
> i get in the following code
>
>          javax.xml.parsers.DocumentBuilderFactory dbf =
> javax.xml.parsers.DocumentBuilderFactory.newInstance();
>          javax.xml.parsers.DocumentBuilder db =
> dbf.newDocumentBuilder();
>
> the Exception
>
> sealing violation
> 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
>
org.apache.xerces.jaxp.DocumentBuilderImpl.<init>(DocumentBuilderImpl.java:9
8)
>
>  at
>
org.apache.xerces.jaxp.DocumentBuilderFactoryImpl.newDocumentBuilder(Documen
tBuilderFactoryImpl.java:87)
>
>  at cosima.components.gateway.bluetooth.Main.main(Main.java:67)
>
> Does anybody know why? I only get this Message using JBuilder.
> using CommandPrompt and JDK1.3.1 everything works fine.
>
> I use Xerces in different Versions. With each of them I get the same
> result. I already have checked file Manifest and found no Sealed: true
> entry.
>
> Thanks
> Hans Georg
>