This content has been marked as final. Show 2 replies
My colleague is having the same problem. He just upgraded Weblogic 5x to 6.1 and is migrating customizations to a Documentum (wdk -- a web app) application. My first thought is, "did he inherit a new Java API on the upgrade where the signing of classes is implemented differently?" I would appreciate any advice. Following is colleague's cry for help:
"I am not installing a bundled application like .war or .ear file. This application is in exploded format and i am slowly migrating it...Trial&Error mechanism !!
I am now getting the following Error [for almost 1 hr] when i load the page..If you know something abt it please let me know..
<Oct 1, 2003 2:25:48 PM CDT> <Error> <HTTP> <[WebAppServletContext(7386397,docne
t,/docnet)] Servlet failed with Exception
java.lang.SecurityException: class "com.documentum.wc.env.DwConfig"'s signer information does not match signer information of other classes in the same package
at java.security.AccessController.doPrivileged(Native Method)
I solved this.
I had 2 copies of the same class file in 2 different JAR files.
The really strange thing was, that both were signed with identical certificates so the signer should've been the same anyways.
But I deleted the classes from one of the JAR's, resigned it, and it worked. Go figure!
So do a search through your entire classpath, looking for classes in the package com.documentum.wc.env.
The error implies that you've at least one class from that package, within a signed jar.