&quot;kabir.khan(a)jboss.com&quot; wrote : | &quot;adrian(a)jboss.org&quot; wrote : | | In fact, I think the first part of your post would be better implemented by listing | | all existing modules at aop initialization? | | That way you don't depend upon the specific bootstrap implementation. | I'm not sure what you mean here? If you mean adding a method returning a map of all loaders and modules, then I think that means AOP will need to come last in the bootstrap? Otherwise as now, it will not pick up the loaders for bootstrap deployments deployed after aop. | What is different between that and using the bootstrap if you are asking the question part way through the bootstrap process? Maybe a better mechanism would be to use the in/uncallback to be notified of the Modules as they are constructed/destroyed. That is in fact how they get registered with the ClassLoading anyway. from bootstrap/classloader.xml | <bean name="ClassLoading" class="org.jboss.classloading.spi.dependency.ClassLoading"> | <classloader><null/></classloader> | <incallback method="addModule" state="Configured"/> | <uncallback method="removeModule" state="Configured"/> | </bean> | Although you would want them at "Installed" when they are actually usuable rather than "Configured". View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204704#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...