[297] Add support for server to client updates

CamilleLetavernier commented 5 years ago

Add a method to ActionDispatcher to send actions to the client directly
Add a mapping from clientId to GLSPClient in the new GLSPClientProvider API
- I'm not 100% satisfied with this: the client ID is specific to each client, so the same clientID can exist in different instances of GLSPServer. However, all instances of GLSPServer use the same GSLPClientProvider so they currently conflict with each other. We could register a (GLSPServer, clientId) pair instead to avoid this issue. On top of that, the clientID is not initially known to the GLSPServer; it's only known when we receive the first message (Typically OpenModel, I guess), so I'm not sure when/where's the best place to register this ClientID - to - GLSPClient mapping

CamilleLetavernier commented 5 years ago

However I was not able to properly test with the dev example. I assume you tested it with papyrus-gefx-glsp?

Yes; and the work on that side isn't complete so it's not published either. So I guess you can't test it directly :(

I've replaced the Syserr with a runtime exception

tortmayr commented 5 years ago

Not sure why but CI is failing for this. The problem seems to be related to the node build, which is especially weird.

tortmayr commented 5 years ago

@CamilleLetavernier, unfortunately this PR is now conflicting with the master branch.

tortmayr commented 5 years ago

Rebased onto current master

eclipsesource / graphical-lsp