Created
May 1, 2019 17:42
-
-
Save nbhusare/ac9f009dd65f5c6affd410bedc6cb697 to your computer and use it in GitHub Desktop.
EMF Containment proxies
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Behavior of EMF when proxy resolution is turned on - It is only when proxy resolution is enabled on a containment reference that the container and contained objects can reside in different resources. In this situation, adding an object to a resource’s contents does not automatically remove it from its existing container. this behavior is only available beginning in EMF 2.2. | |
| Also, when generating a model, "containment proxies "must be enabled explicitly for the whole model, or else all containment references will be considered non-proxy-resolving, completely disabling cross-resource containment. | |
| Previous to EMF 2.2, you could always be sure that the resource of an EObject in a containment tree would also be the resource of its container. Enabling cross-resource containment breaks this assumption, which could impact existing applications. For example, saving an object’s resource does not guarantee that its contents are saved. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment