"ALRubinger" wrote : | Can't Have it Both Ways: | | "scott.stark(a)jboss.org" wrote : ...legacy deployers like ejb2 and the war deployer still have way too many dependencies on other jbossas pieces to pull out. | | | | The Ejb3Deployer does have other integration pieces like JBossASDepdencyPolicy, JBossASKernel, Ejb3JBoss5Deployment, so those would have to be separated out into another layer and injected when configured for jbossas. | | In other words, in the present setup we cannot simply move the deployers out of AS as they're needed by other AS components. We also cannot update them from the EJB3 Plugin in subsequent EJB3 releases. So we're stuck in an undesirable situation. | There is no reason to move all deployers out. Move the ejb3 deployers out into a separate project and ensure that the policy elements that need to be overridden like the dependency, kernel and deployment view have a proper spi that can be implemented by the runtime environment. That is all I and Adrian are saying as far as I can see. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4163449#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...