&quot;adrian(a)jboss.org&quot; wrote : | It should just be a case of adding an attribute to beanfactory to override the hardwired GenericBeanFactory implementation class? Do we leave it completely to the user if the new factory class doesn't have the right 'shape' to get all those things injected: | /** The configurator */ | protected KernelConfigurator configurator; | | /** The bean class name */ | protected String bean; | | /** The access mode */ | protected BeanAccessMode accessMode; | | /** The classloader */ | protected ClassLoaderMetaData classLoader; | | /** The constructor metadata */ | protected ConstructorMetaData constructor; | | /** The properties Map<propertyName, ValueMetaData> */ | protected Map<String, ValueMetaData> properties; | | /** The create lifecycle method */ | protected LifecycleMetaData create; | | /** The start lifecycle method */ | protected LifecycleMetaData start; | I don't see what much we could do. Perhaps GenericBeanFactoryMetaData::getBeans could return some extended AbstractBeanMetaData where we would override describeVisit method to check if the bean has appropriate hooks to do instantiation with KernelConfigurator parameter, configuration with all those properties, ... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138043#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...