flowable / flowable/flowable-engine
suspendProcessInstanceById question
- Vorherrschende Sprache
- Java
- Sterne
- 9.5k
- Forks
- 2.9k
- Ø Merge
- 7 Std. 8 Min.
- Gemergte PRs (30 T.)
- 2
Beschreibung
i have two listener
`
private static ArrayList executionListeners() {
ArrayList listeners = new ArrayList<>();
FlowableListener activitiListener = new FlowableListener();
activitiListener.setEvent(BaseExecutionListener.EVENTNAME_START);
activitiListener.setImplementationType(IMPLEMENTATION_TYPE_DELEGATEEXPRESSION);
activitiListener.setImplementation("${counterSignListener}");
listeners.add(activitiListener);
FlowableListener nodeEndListener = new FlowableListener();
nodeEndListener.setEvent(BaseExecutionListener.EVENTNAME_END);
nodeEndListener.setImplementationType(IMPLEMENTATION_TYPE_DELEGATEEXPRESSION);
nodeEndListener.setImplementation("${nodeEndListener}");
listeners.add(nodeEndListener);
return listeners;
}
`
activitiListener is node start execute,nodeEndListener is node end execute,
i in node A and end listener (nodeEndListener)execute runtimeService.suspendProcessInstanceById() but after node B start listener still execute,and after all listener is execute,include executeListener and taskListener。
and i active process is say have process is active。why?
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Rechercherichtung
Start with the runtimeService.suspendProcessInstanceById call in the node-end listener and trace how the execution and task listeners shown in the issue are ordered. Reproduce the process with node A and node B, then document whether suspension is expected to stop subsequent listeners and identify the exact execution point involved.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- java
- Bereich
- api, backend
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 25/100