Thanks for the pointers. What's the problem with that? Type limitations? 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. I can see how profile service can walk the bean properties and squirrel them aways for safe keeping (assuming they are serializable) but I'm less clear on the startup lifecycle. 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? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249893#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...