I've released EJB3 Core 0.1.2. So now we've got a chicken/egg thing. I couldn't test this against AS because of the API conflict, and Ales couldn't resolve the API conflict until I released. :) Both Anil and I tried Ales' patch in this Thread to resolve AS to no avail. Ales, how'd you like to proceed? You can upgrade AS locally, check your patch by running the new AS TestSuite Smoke tests, and if that's good, push the upgrade on your own. Alternatively you can send me another patch to the "ejb3" module and I'll doing testing and make the final commits. Other projects waiting on this, so this is a bit of a priority. After this is resolved, I'll recommit my changes to introduce EJB3 Proxy into EJB3 Core, and do a follow-up release. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156136#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...