Hello Adrian, Early in the post you indicated that the classloading mechanism was in the microcontainer project but that it wasn't its rightfull place. I wonder if your opinion has changed on this topic? I must admit from my point of view I have the tendency to see the microcontainer as the main mechanism allowing you to host components/containers together. And to me this means that classloading will typically play a critical role in this. I agree that MC does not have to know the exact details (each subsystem could have its own way) but I still imagine that for things to work and cooperate the system would still need some general "rules of engagement". And these rules (things like the specification of the base CL policy mechanism) would have to be specified by MC. Then when someone writes a container it would be clear that, as long as they respect the MC rules, then they have good chances that it will work. Yes, things like classloaders could be separated from MC but then there will need to clarify the various projects that ones needs to be aware of in order to write a workable container. I must admit this is probably a simplistic view (admin tasks comes to mind) and I am still trying to get my head round MC, but still I wonder if your opinion on this has changed or not. Thanks. Gilles. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4124430#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...