| [EVL] Could not locate a metamodel with the URI [message #1726601] |
Tue, 15 March 2016 01:13  |
 Glatz Martin
Messages: 23
Registered: March 2016 |
Junior Member |
|
|
Hello,
I'm facing a problem with the standalone example of an EVL application in combination with the use of a metamodel deployed as eclipse plugin.
If I use the pure evl file and the corresponding run configuration (metamode-url = "http://caex") it works fine, but when I use the Standalone Example and use createEmfModelByURI
@Override
public List<IModel> getModels() throws Exception {
List<IModel> models = new ArrayList<IModel>();
models.add(createEmfModelByURI("CAEX", "models/Topology.xmi", "http://caex", true, true));
return models;
}
it can't locate the metamodel anymore.
I did some debugging, and the problem seems to be that
[b]EPackage ePackage = EPackage.Registry.INSTANCE.getEPackage(metamodelUri.toString());[/b]
if (ePackage == null) {
throw new EolModelLoadingException(new IllegalArgumentException("Could not locate a metamodel with the URI '" + metamodelUri + "'. Please ensure that this metamodel has been registered with Epsilon."), this);
returns null (EMFModel.java)
I was first thinking that I've a format issue of the metamodel-URi, but when stepping through the delegate Registrys and inspecting the keymaps, the only available metamodel was ECore itself.
I did not register my meta-model as EPackage - as soon as I do so, I'm facing again the problem of not being able to call EOperations defined in the metamodel as described in https://www.eclipse.org/forums/index.php/t/1075483/
Is there maybe another option for accessing the "as plugin registered models" instead of createEmfModelByURI , as this one seems to require the EPackage Registration?
Thanks a lot in advance,
Cheers,
Martin
|
|
|
| Re: [EVL] Could not locate a metamodel with the URI [message #1726658 is a reply to message #1726601] |
Tue, 15 March 2016 11:36  |
|
The standalone example is a regular Java application AFAIK, so it cannot use the Eclipse extension registry and therefore has no knowledge of your metamodel.
You probably want to include the metamodel plugin in the classpath of your standalone example, and then register the generated EPackage *through the code generated by EMF* (and not the .ecore, which would produce the issues you mention with EOperations) before you run your E*L script. Off the top of my head, the code would look somewhat like this:
EPackage.Registry.INSTANCE.put(YourPackage.eINSTANCE.getNsURI(), YourPackage.eINSTANCE);
// ... run your E*L script ...
|
|
|
|
Powered by
FUDForum. Page generated in 0.03238 seconds
] 
Search
Help
Register
Login
Home
