I think things got mixed up here. The 'end-complete-process' attribute on
end-state only makes sense in an end-state that appears in a leg of a fork, and
which should end the complete process, see
https://jira.jboss.org/jira/browse/JBPM-1181.
Ending a process does not end the taskInstances,
I tried the following handler, which seems straightforward:
public class EndAllTasks implements ActionHandler {
public void execute(ExecutionContext executionContext) throws Exception {
executionContext.getTaskMgmtInstance().endAll();
}
}
but I'm getting a
look at the end-complete-process attribute on an end node. But iirc, if you
just have one end node that already should happen
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4192010#4192010
Reply to the post :
Using an ActionHandler with taskMgmtInstance.endAll() in the process-end event
should work.
If you experience any issues, please create a unit test, let us know which
version you are working with and show us the exception.
View the original post :
Things did not get mixed up... there is a line missing from my post... probably
wrong quoting again...My first line was:
If you have multiple end-nodes in your processdefinition and there is more then
one token still active when the current token arrives in the specific end-node,
this
