||EJB 2 and J2EE Packaging, Part II|
|Subject:||Classloader can't find common.jar|
Response to: Classloader can't find common.jar
I had pretty much that same set up working in Weblogic 6.1 sp1 and then when I upgraded to sp3, it did not work any more.
It looks like it lost support for the web archive's manifest Class-Path. However, you should not have to explicitly include the common.jar in the war's classpath since the web classloader is sibling to the EJB classloader. Siblings always ask the parent first (unless you specify PREFERWEBINF property in the config.xml definition for the war).