Node Server GModelFactory

[csamarchi]

Hi there,

I have a Node server VsCode extension graphical model going. I am using a YAML file and parsing it with our own parsing method and it is working, I am able to parse our file, loop through, and build instances of our model types and add them to the model state. See the function below:

I'm trying to figure out the next steps and wondering if I'm missing something. Is there another step needed on the server side or is the rest done in the client? I know Node projects do not use GModelFactory, they must be custom, and I think that might be the the next step before rendering/building out on the client side, but wanted to get a better explanation?

Our GModelFactory is following the format of the TaskList example here.

Here is the erroring I'm running into (thought it could provide some extra context):

Any help is much appreciated

[planger]

Hi @csamarchi,

after you have successfully integrated your custom source model, the next step is to generate a GModel with a custom GModelFactory from it.

It looks like your current GModelFactory doesn't set a proper GModel, which is why the error is thrown when the server tries to send it to the client. Once your custom GModelFactory has created a GModel from your YAML files, it needs to set it via modelState.updateRoot(newModel);.

The client doesn't know your YAML files and can only process and render GModels, which are created on the server from your YAML files.

See also https://www.eclipse.org/glsp/documentation/gmodel/

Hope this helps!

[csamarchi]

"@eclipse-glsp/server-node": "0.9.0-next.b178eb2.24"

[tortmayr]

The GLSP documentation is based on the latest release (1.0.0) so I would recommend to update to the release version (if possible):

"@eclipse-glsp/server-node": "1.0.0"

[csamarchi]

I updated to the latest release and used that workaround and still getting same error

[csamarchi]

Any updates to the regression bug mentioned above?

[tortmayr]

Since you are using version 1.1.0 the regression bug mentioned above should not affect you.

[csamarchi]

Also - we are using the Workflow example and TaskList example for our node server vscode extension scenario. I'm aware that the workflow example does not use a GModelFactory instead uses the so-called NullImpl of the GModelFactory. Does that have any affect on our use case?

[planger]

Not really, I think. But in the workflow example, the used SourceModelStorage already writes the source model directly into the model state's root, So the NullImpl of the GModelFactory doesn't need to do that anymore and still everything works.
If you now however replace the SourceModelStorage with an own implementation that "just" writes the source model into the model state, there is still no GModel in it. Therefore, your GModelFactory needs to generate and put it there.

[rsoika]

@csamarchi I have written a short tutorial about the concept of the GmodelFactory and SourceModelStorage. We use a java implementation to load and build our own model. Maybe this can be helpful for your understanding:

https://ralph.blog.imixs.com/2022/05/20/build-your-own-modelling-tool-with-eclipse-glsp/