[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: Scoped beans deployment

[adrian@jboss.org]

"alesj" wrote : 
  | anonymous wrote : 
  |   | Yes, but a missing DESCRIBED dependency should not stop the context
  |   | moving to the new PRE_INSTALL state.
  |   | 
  | 
  | How do you move forward with this dependency?

I don't understand the question?

Let me go through the state in detail and hopefully this will clarify it?

1) Somebody intalls a context that wants to be scoped.
2) This goes through the visitor which builds up the dependencies
and they internally take a reference to the ControllerContext for later use if
required.
3) We check that all "PREINSTALL" dependencies are satisfied,
basically the classloader and in future the classloading dependencies
4) We switch the context to the scoped controller (creating it if necessary)
5) We check that all "DESCRIBED" dependencies are satisfied
(since the classloader has moved to PREINSTALL this will be none by default)
6) Business as usual, except the context is now in a scoped controller.

It's ugly (the switching of the controller), 
but it does allow us to be able to define PREINSTALL dependencies
like the classloading and potentially have seperate DESCRIBED dependencies
using the normal mechanisms.

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

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