Ales Justin [http://community.jboss.org/people/alesj] replied to the discussion "Classloading and caching changes" To view the discussion, visit: http://community.jboss.org/message/543107#543107 -------------------------------------------------------------- First a few questions. The loadClassForParent is a backwards compatibility thing to work around a few issues that the more efficient resource check causes in some edge cases when it delegates to the java classpath. It shouldn't be using it when a Domain delegates to another Domain. That was something we spotted and fixed in 2.2.x, see around line old/new 689/920 http://fisheye.jboss.org/browse/JBossAS/projects/jboss-cl/trunk/classload... http://fisheye.jboss.org/browse/JBossAS/projects/jboss-cl/trunk/classload... Whether it caches things is decided elsewhere, based on the ClassLoaderPolicy rules. This code is just a safety check in the event that the class changes (somebody redeployed a classloader) and the global cache hasn't been flushed properly. As I said on the other response, it can't cache the load in that "globalClassCache", because the classloader used is in the parent domain. It would need some complicated flushing rules to cache it in the child domain as well - not my preferred solution. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/543107#543107] Start a new discussion in JBoss Microcontainer Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]