"speleomaniac" wrote : | Or I am wrong and this would not occur in JBoss MicroContainer.... | It all depends on how you would configure your classloading. e.g. by default - as you might probably know - in JBossAS everything is flat, meaning everything can see everything, and it's the first-loaded rule on which class gets loaded While this is pretty nice/useful for most of the time - I personally liked this very much while I was still a plain user of JBossAS :-) - but of course it can be a pita sometimes. But that's why you have classloading isolation. While in JBossAS itself you have those custom and easy to configure files to apply cl isolation * jboss-app.xml for .ear * jboss-web.xml for .war * jboss.xml for the rest these can be called legacy with the new Microcontainer as the kernel. As part of MC, we completely changed our classloading and deployers layer, making it a lot richer. For classloading, OSGi model was definitely something we looked to support (among other potential new cl models). You can already do most of the OSGi kind of features, only missing on some corner cases. The new syntax is currently supported in jboss-classloading.xml files, while we're already working on making this portable to plain OSGi manifest.mf files. Unfortunately the docs are not that comprehensive: * http://www.jboss.org/index.html?module=bb&op=viewtopic&t=159343 but I do try to answer all of the question releated with MC and therefore its new cl layer in our MC user forum: * http://www.jboss.org/index.html?module=bb&op=viewforum&f=228 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248124#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...