Community
Participate
Working Groups
I have a resource implementing MResource, and EObjects in this resource are referenced by other MSLResource. When a MSLResource references another MSLResource, references are encoded properly. But when the referenced is MResource, it becomes imperative for the implementor of the MResource to encode the reference to EObject's fragment and to decode before resolving.
Created attachment 35160 [details] Fix for this and Bug 128973 Multi-project patch fixing this bug and Bug 128973. The following changes are made: - moved the support for special URI fragments (including a "query" portion for qualified names) into the MSLResource implementation in the compatibility layer. GMFResource now does not do any fragment handling - MSLResource now encodes fragments when saving and decodes them when loading (except for the "fragment query" part) - MResourceFactory (the compatibility resource factory) class now implements IExtendedResourceFactory to provide the name and qualified name support required by EMFCoreUtil for proxies - for non-compatibility resources, EMFCoreUtil now provides empty strings for proxy names and qualified names, as formerly only occurred when the fragment query was absent - MSLResource now saves fragment queries in the EMF way (book-ended by ?s) while still supporting the single ? legacy format
Reviewed and applied patch
[GMF Restructure] Bug 319140 : product GMF and component Runtime EMF was the original product and component for this bug
