java.lang.SecurityException:- sealing violation

843811

i m writing a client for EJBs which receives XML from EJB, parses it and then use the information. while parsing it gives the following exception.

while the same parser is used in EJB deployed in WebLogic works well ....

any one know please help me ....

Parser: parseSchedule() called
java.lang.SecurityException: sealing violation
at java.net.URLClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.access$100(Unknown Source)
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(Unknown Source)
at java.security.SecureClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.access$100(Unknown Source)
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at org.apache.crimson.jaxp.DocumentBuilderFactoryImpl.newDocumentBuilder
(DocumentBuilderFactoryImpl.java:82)
at iac.tango.client.system.Parser.parseSchedule(Parser.java:52)

843811

If you are now doing this from an Applet, the applet needs to be signed.

The XML parser is being passed a URL to make a connection, and start some threads which can be protected functions (depends on the URL).

Signing should fix this problem.

843811

If you are now doing this from an Applet, the applet
needs to be signed.

The XML parser is being passed a URL to make a
connection, and start some threads which can be
protected functions (depends on the URL).

Signing should fix this problem.

Signing has nothing to do with sealing exceptions. Please see this thread:

http://forums.java.sun.com/thread.jsp?forum=34&thread=166234

Vlad.