Mantis - Resin
Viewing Issue Advanced Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
305 minor always 07-12-05 00:00 11-30-05 14:43
Reporter: user62 Platform:  
Assigned To: OS:  
Priority: high OS Version:  
Status: closed Product Version: 3.0.13  
Product Build: 3.0.13 Resolution: no change required  
Projection: none      
ETA: none Fixed in Version: 3.0.15  
Summary: 0000305: Classloader issue when deploying alongside a RAR
Description: RSN-344
I deployed a RAR that shared some of the same libs that my WARs do, and it appears the RAR's classloader pollutes the WAR's classloader. Or at least, the WAR ends up loading classes from the RAR's classpath and then subsequently can't find things that are only in the WAR.

I thought all deployments were supposed to be protected from each other?
Steps To Reproduce:
Additional Information: Windows JDK 5.0_03
Relationships
Attached Files:

Notes
(0000344)
ferg   
07-12-05 00:00   
The webapps are distinct from each other.

However, deployed RARs are intended to be shared in the environment they're deployed to, i.e. a RAR deployed in a web-app would be a JCA resource that would be used by the web-app. A RAR deploy in a host would be used in all of the web-apps.

In other words, the deployed RAR will be added to the environment's classloader as if they were put in the WEB-INF/lib.