-
|
Hello, I've been able to modify the java-emf-theia project template to render graphically an EMF model of my own, which is serialized as XMI. The structure of my modified In my real use-case though, the model is associated to an Xtext grammar, so I need to change the part of the project template that reads XMI models with one that builds the Xtext AST from a file. To do this, I have:
However, it seems that this is not enough, as the system still tries to read mydsl files using the EMF XMI parser1. Can you provide some guidance on how to change the project template to read Xtext model descriptions from files? Thanks in advance! Footnotes |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 9 replies
-
|
Hi Matteo, I think this is because in the java-emf-theia example the GLSP server is executed as a plain Java application and not as an Eclipse application. If you look at the launch config or at what is produced by maven, it is just invoking Thus, you'll need to set up the resource set manually ("StandaloneSetup") and can't rely on the Xtext Eclipse extension points and resource factory registry setup stuff. So I think, you'll need to invoke something like this to create the resource set with which you load your DSL file: Injector injector = new MyDslStandaloneSetup().createInjectorAndDoEMFRegistration();
IResourceFactory resourceFactory = injector.getInstance(IResourceFactory.class);
Provider<XtextResourceSet> xtextResourceSetProvider = injector.getInstance(new Key<Provider<XtextResourceSet>>() {});
XtextResourceSet resourceSet = xtextResourceSetProvider.get();A good place in the EMF GLSP Server is to overwrite I haven't tested this, but that's what I would try. |
Beta Was this translation helpful? Give feedback.
-
Right, that needs to be avoided. Great that you are one step further now!
Hm, no not really from the info I have, sorry! It is definitely missing on the server, the client doesn't know anything about Xtext or the source model from the server. I guess it is some sort of Maven packaging issue or Eclipse classpath configuration issue, if you start the server from the jar or Eclipse, respectively. If you start from jar, do you produce one fat jar? Is there everything that is needed included? Or do you have multiple jars? Then you may need to adjust the classpath parameter when invoking java to ensure including the other jars. |
Beta Was this translation helpful? Give feedback.
-
indeed! The problem is due to L297 of However..... I'm getting closer, but it's not yet finished. Now I get this error 1. Any hints? Footnotes |
Beta Was this translation helpful? Give feedback.
-
|
Ok, I got it. In addition to the Xtext resource factory, the So, the complete code of and all works now! 🎉 🎉 🎉 Thanks again for all the support! I'll create an (accepted) answer summarizing the main points of this discussion asap |
Beta Was this translation helpful? Give feedback.
-
|
Great! I guess you need to register the resource factory for the notation package in Xtext's resource set. |
Beta Was this translation helpful? Give feedback.
-
|
Excellent! Congrats! |
Beta Was this translation helpful? Give feedback.
Hi Matteo,
I think this is because in the java-emf-theia example the GLSP server is executed as a plain Java application and not as an Eclipse application. If you look at the launch config or at what is produced by maven, it is just invoking
TaskListServerLauncher.main.Thus, you'll need to set up the resource set manually ("StandaloneSetup") and can't rely on the Xtext Eclipse extension points and resource factory registry setup stuff. So I think, you'll need to invoke something like this to create the resource set with which you load your DSL file: