This content has been marked as final. Show 1 reply
Did you get a resolution? I have a similar problem with a different object, org.apache.log4j.spi.TriggeringEventEvaluator, which has been loaded by the Weblogic consoleapp. I am running in a standalone server configuration -- admin and application server are the same. Also, using exploded directories.
Is there a way to prevent the WebLogic classloader from loading its version from the consoleapp?