[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: Obtain Kernel from unspecified Context

[ALRubinger]

For follow-up, my solution for EJB3 will be the following:

* Introduce an Ejb3Registry SPI to informally mirror operation naming conventions set forth by JNDI (lookup, bind, rebind, unbind)
* Implement an MC Plugin that conforms to the SPI
* AS Deployers will be responsible for populating the Ejb3Registry with the MC Implementation (ie. put in a reference to the Kernel)
* Unit Tests, Embedded, other runtimes become responsible for providing their own implementations or populating with MC Implementation

This way, EJB3 may become agnostic to the Object Store and hence becomes decoupled from MC, further ensuring that only the appropriate Kernel is in scope (as many may be available within the JVM).

S,
ALR

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4153174#4153174

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4153174