I was not really talking about overrides itself. This should be rather a generic processing extracting domain metadata fragments on a ManagedComponent level, so that they can be used for further processing. I also thought that the deployment metadata would register the namespace for overrides. However i think we should also look at different use cases which don't need a physical deployment - therefore createNewDeployment() - this would still need the meta value transformations, however we don't need to scan existing attachments
Also (d) just adding configuration would be only useful for MC Beans - the reason why this could be interesting is that ProfileService does not know in which deployment a MC bean is located to override it - so we would need to go through all MC beans and check if this fragment applies there. In this case it might be more interesting to add a way to inject a configuration fragment into your MC bean itself.