"adrian(a)jboss.org" wrote : | The first one looks a bit hacky to me. You only recurse until the second to last | property using getters to locate the object then use the setter for the last property. | Hmmm, looking at the code, this doesn't seem that easy/clean to do - doing it in current KernelConfigurator/Configurator notion. The way we currently do this is that we do a PropertyInfo lookup in the Configurator, but the actual target invocation is done outside the property resolution scope. But in our case, we would already need to know the target, in order to execute getters. Or I can refactor ConfigureAction to do this with bypassing KernelConfigurator usage. And perhaps adding warning or throwing exception if name param in Configurator.resolveProperty contains '.'? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4107302#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...