This content has been marked as final. Show 2 replies
How do we go about implementing such an SPI for JBoss 5? Inside the webbeans-ri-int project in the jbossas source tree we have access to the full range of MC connectors.
So long as EJB3 can bring in webbeans-ri-int without introducing a cyclic dependency, the SPI can go there and be implemented by us.
Currently this type of logic lives in an internal registry within AS's "server" module, MappedReferenceMetadataResolverDeployer. Probably on Container start() we can pass the metadata along to an MC Bean which in turn can track the registrations.
Related to this is the issue of making a pluggable resolver for @EJB, which I believe Carlo had either started or has thought about. It's the same mechanism I want to use for MC Integration (@EJB injection into MC Beans).
We'll go into the details as we implement, but wanted to note that we'll need:
public String getJndiName(String businessInterfaceName);
...as JNDI names are specific to a target business interface to be able to support SessionContext.getInvokedBusinessInterface();