|Anonymous | Login | Signup for a new account||02-28-2020 13:38 PST|
|Main | My View | View Issues | Change Log | Docs|
|Viewing Issue Simple Details [ Jump to Notes ]||[ View Advanced ] [ Issue History ] [ Print ]|
|ID||Category||Severity||Reproducibility||Date Submitted||Last Update|
|0000305||[Resin]||minor||always||07-12-05 00:00||11-01-05 14:43|
|Priority||high||Resolution||no change required|
|Summary||0000305: Classloader issue when deploying alongside a RAR|
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?
|Additional Information||Windows JDK 5.0_03|
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.
|07-12-05 00:00||pburleson||New Issue|
|11-01-05 00:00||administrator||Fixed in Version||=> 3.0.15|
|11-01-05 14:43||ferg||Status||resolved => closed|
| Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
29 total queries executed.|
27 unique queries executed.