|[RESOLVED] Get platform package instead of registered package [message #1770949]
||Sat, 19 August 2017 11:09
| Amine Kechaou
Registered: April 2016
Location: Karlsruhe, Germany
[EDIT] I found a way to get around this issue by taking a look at the code of the method prepareBrowseRegisteredPackagesButton in the nested class EcoreActionBarContributor.ExtendedLoadResourceAction |
I'm currently working with EMF Profiles and I have noticed that the packages there are loaded via the EPackage.Registry. The resulting packages' resources have a "http://" URI instead of a typical "platform://" URI, and more importantly reference the generated package and not the main package of the corresponding metamodel (for example EcorePackage, instead of the main package of Ecore.ecore) .
Is there a way to access the main package of the metamodel starting from a generated package?
Concretely, I get an EPackage instance from the EMF Profiles API, which is in fact the generated package, and I would like to access the corresponding metamodel (i. e. the .ecore file)
[Updated on: Wed, 23 August 2017 19:32]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.01499 seconds