"alesj" wrote : | Currently I have a separate binding element, which takes any MC value. This should do it for the injection / dependency, right? | Ok, the binding metadata makes sense from what I said above about keeping the xml simple, but you still need to create the BeanMetaData for the installer pojo. You have to add a context to the MC that does this work and resolves the ValueMetaData objects (e.g. injections). I don't understand why you have visitor callbacks on the Binding/Policy/ScopeMetaData? They are not a part of the BeanMetaData tree so they are never going to get invoked. An alternative to creating a MapMetaData would be to make BindingMetaData extend ValueMetaData so you can set it directly as the value of the PropertyMetaData of the installer pojo? Or more accurately you would need a BindingsMetaData that specializes AbstractSetMetaData to effectively a Set. The PolicyMetaData and the installer pojo could then take a BindingsMetaData. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013033#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...