Why does multiple ejb jars in an EAR share the same classloader whereas each WAR gets its own classloader?
Question
Well, title pretty much says it :). From whatever I have read i know by design EJBs share a single classloader but I am willing to understand the reason behind it. Would appreciate any pointer.
1 answers
solution1
0 2013-03-20 13:14:41
Each WAR is a standalone module. Each JAR in the root of an EAR aswell as the WAR file inside are related modules. Thus it makes sense for them to use the same classloader. Sharing class loader between multiple WAR files would not be feasable.
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.
Related Question
Using same classloader for ear and war
Does each Solr core have its own classloader?
Why Java Classloader does not release jars
Share same JPA persistence.xml across multiple EJB JARs inside EAR
wildfly classloader issue between war's lib and ear's lib
using URLClassLoader gets the same reference as the default ClassLoader
Classloader problem with EJB
Absolute singleton over multiple wars (share classloader)
Share Classloader between multiple in Jetty Maven Plugin
Weblogic - Why Java ClassLoader does not load classes from jars mentioned in empty manifest jar
Related Tags