Hi Remy, I'm not sure if you noticed this, but it looks like making the JPA deployer optional causes some regressions: http://fisheye.jboss.org/changelog/JBossAS/?cs=101922 Carlo and I were discussing this on #jboss-dev, and where thinking a simple fix for this problem would be to switch it back to explicit and have a "NotImplemented/NotAvailable/NotSupported/Noop" service that would use the same name. That service would be used in your standalone config. Any thoughts on this? -- Jason T. Greene JBoss, a division of Red Hat