flowable / flowable/flowable-engine
suspendProcessInstanceById question
- Lingua principale
- Java
- Stelle
- 9.5k
- Fork
- 2.9k
- Merge medio
- 7h 8m
- PR unite (30g)
- 2
Descrizione
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?
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- java
- Ambito
- api, backend
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 25/100