"emuckenhuber" wrote : | Well i do persist everything. Also null values, because i think it should be possible to change the value to null (e.g. for a String) ? | What i mean is more or less a isEdited flag - so that i can differentiate between values which are from the original deployment descriptor | (which do not need to be persisted) and changed values. | ... | And i think we also need a isRemoved flag for the ManagedProperty. | e.g. if you have a list of properties and you want to remove one property | we would need to persist that too and remove that when updating the persisted attachment... | Ok, I'll add isEdited and isRemoved/remove notions. "emuckenhuber" wrote : | Hmm what i mean is that if you have a collection of ManagedObjects which represent for example your datasources or beans. | And you update one of them it would be good to have a identifier to see which ManagedObject to update. | Because if the order of this collection (for some reason) changes, it will just change the properties of a different bean or datasource. | Making the ManagedObjectID required and immutable, would help to identify that again... | Not sure if there is a different way to do that ? The problem is that ManagedObjectID is generally derived from a property like the bean name or the jndi name. Your essentially talking about a standard xml ID that uniquely creates an association between the attachment and ManagedObject. We don't specify this today and its too burdensome to require all descriptors be changed to have an id. The problem does exist for changing what the original deployment ManagedObjectID is as well, for example changing the DefaultDS jndi-name to MyDefaultDS. For that we would have to have the original ManagedObjectID. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191492#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...