AndreyCurious opened a new issue, #2414: URL: https://github.com/apache/incubator-kie-issues/issues/2414
## Describe the bug When a Message is renamed or deleted, the editor updates (`drools:msgref`) or clears (`messageRef` + `drools:msgref`) the reference on message events. The list of event types it visits includes `endEvent`, `intermediateThrowEvent`, `startEvent` and `intermediateCatchEvent` — but **not `boundaryEvent`**. As a result, a boundary event with a `messageEventDefinition`: - after **rename**: keeps the old `@_drools:msgref`; - after **delete**: keeps a dangling `@_messageRef` (and `@_drools:msgref`) pointing to the removed root `message` — the file then references a non-existent element and fails to parse on reopen. ## Steps to reproduce 1. Create a process with a Message and a **boundary message event** that references it. 2. Rename the message → the boundary event still carries the old `drools:msgref`. 3. Or delete the message → the boundary event keeps `messageRef` to the deleted message; reopening the diagram fails to parse. ## Root cause In `packages/bpmn-editor/src/mutations/renameMessage.ts` and `packages/bpmn-editor/src/mutations/deleteMessage.ts`, the condition that selects message-bearing flow elements omits `boundaryEvent`. ## Suggested fix Add `boundaryEvent` to that condition in both files, so boundary message events are updated/cleaned like the other message events. ## Environment Apache KIE BPMN Editor, `main`. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
