What is a InitializeClientSession request in version 2.0.0 ?

[rsoika]

Hi,
migrating from 1.1.0 to 2.0.0 I stumbled over a problem with the old java method configureClientActions in my DiagramModule. I used this method to bind my custom action which is send between client and server to inform about model changes:

    @Override
    protected void configureClientActions(MultiBinding<Action> binding) {
        super.configureClientActions(binding);
        binding.add(BPMNPropertyPanelUpdateAction.class);
    }

The release notes state: Remove configureClientActions from DiagramModule as client actions are now implicitly configured via InitializeClientSession request

Can someone give me a short example how my code should look like in version 2.0.0 ?

[tortmayr]

Hi @rsoika,
we a currently still in the progress of updating the documentation for GLSP 2.0 and will also provide a Migration guide that will
cover the necessary adaptions from 1.0.0 to 2.0.0 in detail.
I would recommend to wait with the upgrade to 2.0.0 until this migration guide is available.

[rsoika]

Ok no hurry ;-)

[rsoika]

Hi @tortmayr, I know I'm a little impatient. But does this change simply mean, that I no longer need to bind my custom action in the method configureClientActions on the server side, and it simply is sufficient that my client module configures the corresponding action handler and will now automatically react when my server sends this kind of action?

export const BPMNPropertyModule = new ContainerModule((bind, _unbind, isBound, rebind) => {
    bind(BPMNPropertyPanel).toSelf().inSingletonScope();
    bind(TYPES.IUIExtension).toService(BPMNPropertyPanel);

    configureActionHandler({ bind, isBound }, BPMNPropertyPanelUpdateAction.KIND, BPMNPropertyPanel);
});

[tortmayr]

Hi @rsoika,
yes that is correct. The client now sends a list of all handled action kinds to the server in the initializeClientSession Request.
This means it is no longer necessary to explicitly configure Client Actions on the server side. You can simply dispatch any action on the server that has a registered client handler (or command) and it will be automatically forwarded to the client.