[
https://jira.jboss.org/jira/browse/JBPM-1774?page=com.atlassian.jira.plug...
]
Alejandro Guizar commented on JBPM-1774:
----------------------------------------
Alternatively, we can introduce a new cancel-tasks attribute which does just that, to
avoid altering the existing behavior. Specifying both end-tasks and cancel-tasks can be
rejected as a parse error.
end-task attribute should cancel tasks instead of ending them (and
thus have a different name)
----------------------------------------------------------------------------------------------
Key: JBPM-1774
URL:
https://jira.jboss.org/jira/browse/JBPM-1774
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Engine
Affects Versions: jBPM 3.2.3, SOA 4.2 CP02
Environment: N/A
Reporter: Ronald van Kuijk
Priority: Minor
Fix For: jBPM 3.3.2 GA
The end-tasks attribute on a task-node is used to end tasks that are not ended when the
task node is left and no blocking tasks exist. These non-blocking tasks should (imo) be
cancelled and not ended. So the attribute should also chance from end-tasks to
cancel-tasks
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira