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

[adrian@jboss.org]

"adrian at jboss.org" wrote : 
  | I think that what we should really do is have a notion of ScopeKey in the 
  | BeanMetaData[Factory] and the ControllerContext.
  | 

Essentially what I'm saying is what is done now in the DescribeAction
(mostly delegating to the MetaDataRepository to determine default rules)
should be done at (pre-)installation time.

We would essentially implement the default rules in the AbstractBeanMetaData
(so they can be overridden).

The difficulty comes in the notion of the scoped kernel.

Before we can do the install, we need to create the scoped kernel
and for that we need metadata scope to exist so we remember the scope.
(There's also potentially a race condition here with two threads trying
to create the same scope - but that's another story).

I think the solution is for the BeanMetaData to fully describe itself
and then have the install/uninstall into the root kernel do the work
from the description (again mostly delegating the KernelMetaDataRepository).

The difference being that the install/uninstall just "does it" based
on what the BeanMetaData tells it, it doesn't make any policy decisions.

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

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