-
I have implemented an This seems to be only for Server Actions. Other custom client Actions are received and handled as expected. The implementation of the @injectable()
export class BPMNPropertyPanel extends AbstractUIExtension implements IDiagramStartup, ISelectionListener, IActionHandler {
...
handle(action: Action): ICommand | Action | void {
console.log(' === handle action: ' + action.kind);
}
...
} The export const BPMNPropertyModule = new FeatureModule((bind, unbind, isBound, rebind) => {
bind(BPMNPropertyPanel).toSelf().inSingletonScope();
bind(TYPES.IUIExtension).toService(BPMNPropertyPanel);
.....
configureActionHandler({ bind, isBound }, BPMNPropertyPanelUpdateAction.KIND, BPMNPropertyPanel);
});
export {
....
BPMNPropertyPanel,
BPMNPropertyPanelUpdateAction
} from './bpmn-property-panel'; And finally I register my Feature Module in the initializeDiagramContainer method of my DiagramModule export function initializeBPMNDiagramContainer(container: Container,
...containerConfiguration: ContainerConfiguration): Container {
return initializeDiagramContainer(container, bpmnDiagramModule, helperLineModule, BPMNPropertyModule, ...containerConfiguration);
} From my debug code id looks like my |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
ok, I found the problem. It had nothing to do with the Feature Module. actionDispatcher.dispatchAfterNextUpdate(new BPMNPropertyPanelUpdateAction()); I solved the problem by replacing the call with: actionDispatcher.dispatch(new BPMNPropertyPanelUpdateAction()); This was some code fragment form my earlier implementation with GLSP 1.x. Maybe things have changed in my code base and now in my current context it seems not longer to be useful to call |
Beta Was this translation helpful? Give feedback.
ok, I found the problem. It had nothing to do with the Feature Module.
The reason was that I created my action on the server with:
I solved the problem by replacing the call with:
This was some code fragment form my earlier implementation with GLSP 1.x. Maybe things have changed in my code base and now in my current context it seems not longer to be useful to call
dispatchAfterNextUpdate
. I guess there was somewhere aUpdateModelAction
in my code before that I removed during the migration to GLSP 2.x