1 of 1 people found this helpful
.war deployments are supposed to have isolated classloader as per spec. What that means is, other (sub)deployments and/or classes outside the .war, won't be able to access classes within the .war. If that "foo" class wants to access a class in the .war, then that "foo" class has to be present within that .war.
Thank you for the quick reply.
So you mean if I have a jar named ABC in which class "DEF" wants to access a class "GHI" that is present in war XYZ , I will have to place the jar file in the lib of war file. Kindly let me know if I have understood right or is there any other way to do this.
ABC should be in the WAR. Perhaps you could also pack GHI in a jar JKL and place both ABC and JKL in the ear lib and they might see each other.