[Backport 1.3] Trigger boundary events after an interrupting event subprocess is triggered #9242
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* if an interrupting event subprocess is triggered then remove the subscriptions of other event subprocesses in the same flow scope * but don't remove the subscriptions of boundary events that are attached to the scope * the boundary events can be still triggered because they are attached to the scope and are not inside of it (cherry picked from commit 7c76eeb)
* remove methods from event scope instance state that are only used in tests but not in production code * these methods were used previously but are not needed anymore (cherry picked from commit 17a66f6)
* migrate the test case from JUnit 4 to JUnit 5 using the Zeebe state extension (cherry picked from commit 2851144)
* handle interrupting event subprocesses and interrupting boundary events differently by introducing boundary element ids * an interrupting event subprocess interrupts the event scope, but it can still be triggered by boundary events * after an interrupting boundary event is triggered, no other event can be triggered for the event scope (cherry picked from commit 07cca46)
(cherry picked from commit f87e8f1)
(cherry picked from commit 5a449a7)
(cherry picked from commit c57ced5)
(cherry picked from commit 84c267f)
(cherry picked from commit be2d3d6)
(cherry picked from commit 7791618)
|
@pihme please accept the PR 😅 It is a pure backport of the original PR, expect one small change (last commit) to make it compatible with Java 11. |
|
Build failed: |
|
bors merge |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Backport of #9175
Related issues
relates to #6874