It's part of the core java security model. If a package is sealed within a jar then packages of the same name cannot be defined in another jar, or elsewhere on the classpath.

Within the manifest file of the jar file which is being loaded by your putpr servlet you'll probably have a couple of lines like:

Name: nu/xom
Sealed: true

The XOM jar that I have (xom-1.0d8.jar) doesn't seal its packages. So, you need to find the jar which is sealing the nu.xom package and stop it doing so. (Or work out your xom dependencies)

Regards,

Jon

Pawson, David wrote:
From the log

2004-11-02 09:24:51 StandardContext[/servlets-examples]SessionListener: contextInitialized() 2004-11-02 09:25:52 StandardWrapperValve[putpr]: Servlet.service() for servlet putpr threw exception java.lang.SecurityException: sealing violation: can't seal package nu.xom: already loaded at java.net.URLClassLoader.defineClass(URLClassLoader.java:234) at java.net.URLClassLoader.access$100(URLClassLoader.java:55) at java.net.URLClassLoader$1.run(URLClassLoader.java:194) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:187)



Any help appreciated.


Regards DaveP.

**** snip here *****




--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to