I checked in just enough changes to allow the default AbstractManagedObjectFactory to build a ManagedObject set for a KernelDeployment. In reality the BeanDeployer should be implementing the ManagedObjectCreator.build method as the deployer has the metadata and understands things like annotation overrides. Its not clear to me that the BeanInfo beanInfo = configuration.getBeanInfo(clazz) call used by the AbstractManagedObjectFactory is going to have the beans.xml annotations/overrides applied. Would it? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4087705#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...