"alesj" wrote : | Or I can refactor ConfigureAction to do this with bypassing KernelConfigurator usage. I have a few question regarding this impl: | protected void dispatchSetProperty(PropertyMetaData property, boolean nullyfy, BeanInfo info, Object target, ClassLoader cl) | throws Throwable | { | String name = property.getName(); | if (nullyfy) | { | info.setProperty(target, name, null); | } | else | { | PropertyInfo propertyInfo = info.getProperty(name); | ValueMetaData valueMetaData = property.getValue(); | Object value = valueMetaData.getValue(propertyInfo.getType(), cl); | info.setProperty(target, name, value); | } | } | This bypasses the KernelControllerContextAction.dispatchJoinPoint, which is probably not a good thing. But on the other hand, every BeanInfo.get/set or PropertyInfo.get/set also doesn't go through JoinpointFactory. What's the main purpose of JoinpointFactory then? To simplyfy AOP usage or to add some other metadata notion? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111725#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...