"adrian(a)jboss.org" wrote : The parsing available in the metadata project (from ejb-jar.xml and jboss.xml) | should be enough to write your tests (using the same hooks that the deployers | use to create the real objects). | You don't care how the EJBMetaData gets constructed, that is a policy decision of the | appserver. e.g. parsing annotations, programmatically or something else. This assumes that EJB3 is intended for use only within the AS Environment. The Deployers in question need be an integration point only between jboss-metadata/MC and ejb3/MC, not AS. If I want to start up an Embedded or Standalone EJB3 Environment, I should be able to use the same Deployers, as they depend only on the MC Deployment API and other dependencies of EJB3. "adrian(a)jboss.org" wrote : The individual projects should not depend upon the appserver's deployers | or even the deployment api. | Use case: If I want to re-use ejb3 programmatically I should just be | able to instantiate the ejb3 metadata and make some call to a factory in the ejb3 | project. The EJB3 Components should not depend on the Deployers, true. Only metadata, and I'm doing a refactoring effort now to create Containers from only the metadata objects. The end result will eventually make programmatic creation of an EJB possible. However, an Assembly of EJB3 Standalone/Embedded should be able to re-use the same Deployers used in AS. That way, we don't have to create the metadata on our own by duplicating the logic already written. "adrian(a)jboss.org" wrote : Deployer and runtime configuration is a policy decision of the appserver. | If I want to swap out, augment or otherwise change how EJBMetaData gets | constructed that is something that is done in the integration project i.e. the AS. AS is not the only target integration project. So configuration is a policy decision of whatever is providing the runtime, and this is achieved by editing the ejb3-deployers-beans.xml file accordingly. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151475#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...