Deprecate usage of org.jboss.ejb3.embedded.deployers.JBossEjbParsingDeployer ---------------------------------------------------------------------------- Key: EJBTHREE-1718 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1718 Project: EJB 3.0 Issue Type: Sub-task Components: embedded Affects Versions: 1.0.0-GA Reporter: jaikiran pai Assignee: jaikiran pai The original idea was to move org.jboss.ejb3.embedded.deployers.JBossEjbParsingDeployer from the jboss-ejb3-embedded to jboss-ejb3-deployers. But after seeing, the code in org.jboss.ejb3.embedded.deployers.JBossEjbParsingDeployer, there isn't much it is doing other than passing on appropriate values to the org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer: public class JBossEjbParsingDeployer extends SchemaResolverDeployer<JBossMetaData> { public JBossEjbParsingDeployer() { super(JBossMetaData.class); setName("jboss.xml"); } } So instead of moving the deployer, let's deprecate this and instead use the org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer in jboss-ejb3-embedded with proper configurations in *-beans.xml: <bean name="JBossEjbParsingDeployer" class="org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer"> <constructor> <parameter class="java.lang.Class">org.jboss.metadata.ejb.jboss.JBossMetaData</parameter> </constructor> <property name="name">jboss.xml</property> <!-- We need to be fast, so no schema validation --> <property name="useSchemaValidation">false</property> </bean> Note that, at a later point in time we will need a new JBossEjbParsingDeployer in ejb3-deployers project which integrates with the org.jboss.deployment.JBossEjbParsingDeployer -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira