[jboss-dev-forums] [Design the new POJO MicroContainer] - Naming, @JNDI and OnDemand

[alesj]

WRT
 - initial ml post: http://lists.jboss.org/pipermail/jboss-development/2008-November/012997.html
 - the latest ml post (where Adrian moves his code to svn): http://lists.jboss.org/pipermail/jboss-development/2009-May/014341.html

A few questions after checking the code.
(1) 

  | /**
  |  * JNDI.
  |  * 
  |  * TODO move to AS integration project
  |  * @author <a href="adrian at jboss.com">Adrian Brock</a>
  | 
Where exactly would you wanna move this?
What should we do with "duplicated" @JndiBinding in AOP-MC-int?

(2) Why do we have two diff impls AbstractJNDILifecycleCallback, when they do exactly the same?

(3) Basically the OnDemand test is completely broken. :-)

By default it was passed an AUTOMATIC mode,
which meant it was never really On_Demand.

Once I fixed this, there is this problem with @JNDI and On_Demand.
@JNDI matches AOP lifecycle, which needs a _real_ state (not Not_Installed) in order to kick in.
Whereas the OnDemand beans just stay at Not_Installed,
meaning they will not get "intercepted" by @JNDI lifecycle hooks until they move fwd.

What to do? :-)
(a) have OnDemand stay in Pre_Install
(b) add extra Not_Installed AOP lifecycle hook



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

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