I'm also putting AOP beyond scope for 3 reasons:
1. Can't get an unit test to work in surefire (/maven2)
2. Both EJB3 container and client launcher don't need the extra functionality
3. Can't think of a proper bind-cut without recurssion into the injection framework
It should be easy to create a separate module which does injection with
We'll lose the possibility to have a POJO injection classloader.
Is there a question here or this is just the plan? As an integration piece, I would think we want an mc dependency injection handler so that an injection reference does result in a property dependency relationship.
Correct, the MC injection & dependencies are done in the setup phase.
So for example if SessionBean1 wants SessionBean2 injected then SessionBean1 container is registered as being dependant on SessionBean2 container, which will start and put SessionBean2 in JNDI... MC starts SessionBean1 container, put SessionBean1 in JNDI, setup JNDI env (java:comp/env/SessionBean2 -> java:global.ear/SessionBean2/local) and then start the injection phase (java:comp/env/SessionBean2 -> SessionBean1.bean2Interface).
To summarize scope: injection framework does (EJB3) bean injection, while the container (EJB2 + 3) work with MC for dependency injection.