http://jira.jboss.org/jira/browse/EJBTHREE-1249

I guess the spi should live in jboss-ejb3-ext-api under org.jboss.ejb3.resolver package.

The Ejb3Deployment needs to be updated to allow injection of the spi for the EjbModuleEjbResolver, EjbModulePersistenceUnitResolver and MessageDestinationResolver.

These will be the default implementations of the spis initialized in the ctor with the expectation that the integration code will override as needed.

in going through the ejb deployer resolver its really
the existing DeploymentScope interface in core that just
needs to have a couple of methods moved there for
resolution. This is not to the injection layer yet, although
some use of jndi names seems questionable

Updating the DeploymentScope interface to the following looks like it allows the integration code to specifying the resolution logic:

public interface DeploymentScope extends JavaEEApplication
{
 public Collection<Ejb3Deployment> getEjbDeployments();
 void register(Ejb3Deployment deployment);
 void unregister(Ejb3Deployment deployment);

 /**
 * Find a deployment based on its relative deployment name
 *
 * @param relativeName expects "../foo.jar" so expects the .. in front
 * @return
 */
 Ejb3Deployment findRelativeDeployment(String relativeName);
 /**
 * Obtain the EJBContainer best matching the business interface
 * @param businessIntf - the business interface to match
 * @return the matching EJBContainer if found, null otherwise.
 */
 EJBContainer getEjbContainer(Class businessIntf);
 /**
 * Obtain the EJBContainer best matching the business interface
 * @param ejbLink - the referencing ejb-link
 * @param businessIntf - the business interface to match
 * @return the matching EJBContainer if found, null otherwise.
 */
 EJBContainer getEjbContainer(String ejbLink, Class businessIntf);

 String getShortName();
 String getBaseName();
}