Just an update, we noticed that the client jar (form the ear) that our web app is using perform spring init via beanRefFactory using the classpath url "classpath*:applicationConfig.xml". Now spring seems to look into all available class loaders and load whatever applicationConfig.xml it finds.
But our question is, why does JBoss allow it to load from another ear's class loader? We already disabled the unified class loader, yet spring can still crossover from our war into another ear to look for configs (refer to the debug output above). Is this class loading behaviour by design? We've already looked at the wiki class loading article at http://wiki.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration. The article doesnt shed any light on this, we've replicated this problem in both 4.0.1 and 4.0.2. Anyone has any comments as to whether this is as per designed or a bug? Appreciate any comments. Thanks. Cheers. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3883297#3883297 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3883297 ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
