"jhalliday" wrote : Thanks for the pointers. | What's the problem with that? Type limitations? | Basically all values of ManagedProperties are exposed as a MetaType and MetaValue pair consisting only of simple types. As this is a very generic processing it could happen that in some cases we cannot recreate the actual object, if we don't have additional information (e.g. a MetaMapper). That's why it would be good to review what's exposed and provide additional mappings if needed. This really depends on the complexity of e.g. your TSConfigurationBean. "jhalliday" wrote : | I definitely don't want a compile time dependency on profile service, so it looks like using annotations in the -beans.xml is the way to go. | Hmm i've never tried to put property annotations for profileservice in the -beans.xml directly, but should work. That's also why we are also working on a xml descriptor for this view. "jhalliday" wrote : | What's the relationship between MC injection and profile service overriding the values using those from it's saved settings? I need very specific timing - the values must be set before certain events in the startup sequence if the value set is going to have an effect. When is this currently done and is there a way to control it? The persisted changes will get applied to the BeanMetaData directly before the bean is handed over to MC and installed - so before the bean is instantiated. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249902#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...