At the moment the lifecycle callbacks are driven by KernelControllerContextAction. I could move this into the AbstractControllerContext.install() and uninstall() methods. That should make it available to all types of contexts? Assuming that they extend AbstractControllerContext of course. The main problem with this is that the lifecycle metadata stuff lives in BeanMetaData which is in the kernel project and so is not visible from the AbstractControllerContext. If I have understood you correctly, this would then need to be moved out or changed into something else that is usable by AbstractControllerContext? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028361#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...