"adrian(a)jboss.org" wrote : | 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. What all should we describe (prepare) besides the Scopes (to create the ScopeKey) from annotations on BeanMetaData? What about the things we already do in DescribeAction? Should be moved to this preparation stage as well? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015071#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...