"alesj" wrote : Using KernelConfigFactory to get KernelConfig (which can provide this)? | | Putting KernelConfig instance into Configurator? | It's a 'loop' usage. Looks wrong. | | I see we are already using KernelConfig as a parameter. | Doing it the same here (adding it as a parameter in resolveProperty method)? | If I do this (just tried), then almost every method in Configurator needs it. Yuck. | | Any other ways / ideas? | It is the KernelConfigurator that has this information. The problem is that the current code uses a static singleton as a delegate AbstractKernelConfigurator -> Configurator so one way to fix would be to move the code to the AbstractKernelConfigurator that needs kernel specific config. Perhaps a simpler solution is to expose the TypeInfoFactory on the TypeInfo interface. You would then be able to do | TypeInfoFactory typeInfoFactory = beanInfo.getClassInfo().getTypeInfoFactory(); | TypeInfo typeInfo = typeInfoFactory.getTypeInfo(name, classLoader); | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002844#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...