One of the failures i mentioned was about restoring JMS destinations. The updates does not work when the ManagedObjectClass(..) is not present in the deployment descriptor. So the tests with this annotation element are passing, the one without is failing. One other problem i think we could have is that ManagedObjectFactory.initMO does not create the same output, as ManagementView (as this would require e.g. KernelDeploymentManagedObjectCreator) Additionally the failures which can be seen during the bootstrap (https://jira.jboss.org/jira/browse/JBAS-6524) seem also somehow related to this - as when processing the collection in the ManagedObjectFactory, does not have access to the ComponentDeploymentContext.getMetaData() for each bean. Not really sure about this, as it's been a while since i last looked into this. So the main issue with that is when restoring the persisted information it is (of course) relying on the same ManagedObject structure as it was persisted before. Only the values are getting persisted and restored (which makes sense, as the metaType should not change) Therefore i think that this kind of 'override' done by the InstanceClassFactories (getManagedObjectClass), should be done outside the deployers - e.g. in ManagementView when creating the ManagedComponents. So that it always creates the same MO for the attachment persistence. Maybe a related topic Scott created: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222668 This does not not cover partial persistence and removing components, but i think we can discuss that later. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225465#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...