So we'll build up a new common metadata component in projects/??/jboss-metadata which combines EJB 2 and EJB 3 metadata (and also has JavaEE metadata). (It's weird that you had to extend EJB 3 metadata to accommodate EJB 2, because EJB 3 should be 100% backwards compatible.) Then in trunk we build up the deployer chain: EjbAnnotationParsingDeployer -> EjbParsingDeployer -> JBossEjbParsingDeployer. Then the component deployers should pick up the meta data and fire off new meta data for container deployers. I think the component deployer should also register virtual supply/demand dependencies, or is that in the container deployers? EjbDeployer and Ejb3Deployer (was EJBStage2Deployer) -> Stateful3ContainerDeployer etc. That way an EJB 3 deployment can have EJB 2.1 CMP & BMP (spec chapter 8, 9, 10 & 11). Maybe we can do with one EjbDeployer. To be able to use aop.xml we'll do some trickery in the container deployers. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057659#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...