glsp-vscode-client and node server

[csamarchi]

Hello, I've been trying to get the glsp-vscode-integration workflow example working with the glsp-node-server. I made a few adjustments inside the workflow-extension.ts file and it seems to be connecting to the server. See below screenshot

However when I go to run the Worklfow GLSP Extension Example as it says to do, it is empty. Not seeing anything. Not seeing any error logs in the debug terminal either.

These are the steps I've ran to produce:

1. yarn install and yarn build inside the client directory
2. yarn install and yarn build and yarn start:server inside the node server directory
3. Open VS Code (for client) and run Workflow GLSP Example Extension (this works for me when running with the java server but not the node one)

Can anybody help me with this? Any debugging ideas? Anybody tried getting the glsp vscode extension working with the glsp node server?

[tortmayr]

Hi @csamarchi,

Not seeing anything. Not seeing any error logs in the debug terminal either.

The GLSP diagram editor is running in an isolated webview. Log messages of this webview are not logged in the debug view.
However you can use the Developer Tools (Help -> Toggle Developer Tools) inside of the runtime VS Code instance. Then you can check for errors in the Console tab.

Can anybody help me with this? Any debugging ideas? Anybody tried getting the glsp vscode extension working with the glsp node server?

We recently added a project template to the GLSP examples repository that demonstrates how to use the VS Code integration with a node GLSP server. Using this template as baseline you should be able to adapt it for the workflow example with only minimal changes.

I can only make an educated guess at this point but in general your approach and the changes you posted look fine to me. Could be a dependency resolution issue. In the project template we use webpack to bundle the server sources into a single minified file. Maybe you should use the same approach for the workflow example and then update the executable path so that it points to the packed .js file.