"bdecoste" wrote : The "magical plugin" is a stopgap until we are thirdparty jars like everything else. Nobody is stopping you from making the ejb3 core code coming into AS as thirdparty. What I do not understand is why should the interceptors (which as AS integration code) sit in the externalized project? Like Adrian said, interceptors etc are integration code and should be in AS, tomcat or any other container workspace. Additionally, the ejb3 tests that require AS, should be in the AS workspace. The external project that houses the core ejb3 code should just test ejb3 code with junit/JBossTest. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135039#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...