There is a bit of a mismatch with the migration to the BeanMetaDataFactory as the preferred KernelDeployment approach to describing the beans in the deployment and BeanMetaDataBuilder only providing access to a BeanMetaData instance. One either has to test whether the resulting BeanMetaData is a BeanMetaDataFactory (and for the default BeanMetaDataBuilder which returns an AbstractBeanMetaData it is), or use the deprecated KernelDeployment.setBeans. Can we add a way to get hold of a BeanMetaDataFactory from the BeanMetaDataBuilder to avoid this? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4163953#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...