"emuckenhuber" wrote : | Although i think this would also require that ManagementView just pass the changed values to the deploymentRepository. | That is what is happening already though since the input is the ManagedComponent that was updated. We would only be writing out properties that have non-null values. I suppose this should go further and only write out properties that were explicitly updated, is that what you mean? We would need an isEdited flag on ManagedProperty for that. "emuckenhuber" wrote : | Furthermore it makes the ManagementObjectID immutable. As there needs to be a identifier to merge a collection of managed objects!? I don't follow. For a KernelDeployment for an mcbeans deployment, there is: ManagedObject(KernelDeployment) + beanFactories = ManagedObject[](BeanMetaDataFactory) where each BeanMetaDataFactory has a beans property of type ManagedObject(@ComponentType={MCBean,*},BeanMetaData)[] for the mcbeans compoment that maps to a ManagedComponent. The id is the name of the bean for the components, for the factories it would have to be the index in the array. Are you talking about the id changing from Bean1 to Bean1.1? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191486#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...