I see your difficulty, but for the reasons stated above, we can't just implicitly start exporting the default package since that could reveal "module private" classes that the user doesn't want to be shared. Wouldn't it make more sense to have these "java.xxx proxies" in some jboss aop package that its classloader explicitly exports and define then against jboss aop's classloader? That way your not going to interfere with the import/export rules of the user classloaders. I guess the question Is what is the reason why you define these classes against the user classloader instead of having one implementation against the jboss-aop classloader or even the system classloader? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204758#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...