"charles.crouch(a)jboss.com" wrote : | So overall the most important thing is to have property.setRemoved() cause nothing to be persisted for the managed property, and that a default (if specified somewhere) is applied to the actual running instance. [This could just be letting the component itself choose the default, I don't think it has to come from the ManagedProperty annotation for CR1, though it would make sense in the future.] This is what I see as the core issue that needs resolving for CR1. | | If we don't have this function for managedproperty's which are primitives then that's not great, but I don't necessarily see it as a blocker since there probably not that many such properties. That a removed property has no value applied to the metadata and the metadata simply defaults to a value will apply to all managed property types, including primitives. Is that the function you are questioning? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223090#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...