"adrian(a)jboss.org" wrote : | Ok with me. Your "workaround" looks horrible. :-) | I know, just needed something to get me going without having to update too many snapshots. "adrian(a)jboss.org" 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. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203654#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...