Closed mboskamp closed 9 months ago
The 7.20 backport is missing and will happen after the master PR is merged.
Reopened to move the logic that creates a joined map (of builtinTaskListener and regular taskListener) into another method that is not as frequently called as the TaskDefinition#getTask method and improve the docs.
Environment (Required on creation)
Any Camunda version
Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket)
When registering multiple builtin task listeners with BPMN parse listeners using customPreBPMNParseListeners and customPostBPMNParseListeners, the order of the task listener is not always consistent.
During normal BPMN execution via the process engine, the order is reversed (first post, then pre). After process instance modification, the listener order is not reversed (first pre, then post).
Steps to reproduce (Required on creation)
customPreBPMNParseListeners
and one ascustomPostBPMNParseListeners
Observed Behavior (Required on creation)
During normal execution of the process, the task listener registered through the
customPostBPMNParseListeners
fires first, the other task listener second. After process instance modification, the task listener registered through thecustomPreBPMNParseListeners
fires first, the other task listener second.Expected behavior (Required on creation)
The task listener registered through the
customPreBPMNParseListeners
always fires before the task listener registered throughcustomPostBPMNParseListeners
.Root Cause (Required on prioritization)
Solution Ideas
Hints
Links
Breakdown
Dev2QA handover