Doesn't this just fix visibility of the classloader from other loaders in the repository? I checked the AOP implementation, and it is currently doing the same process of manually flushing the blacklists. I ended up having to create a child URLClassLoader to catch the transient classes, since I can't pollute the top level CL that is present at deploy time (else classes referenced by the one I am generating will end up conflicting with the ones loaded by the tomcat CL). So this obviates my specific need. However it is possible that others would run into it, and if there are plans to redesign any of this for the MC, IMO we should consider a public interface for necessary interactions like this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986604#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...