[
https://jira.jboss.org/jira/browse/JBPM-2720?page=com.atlassian.jira.plug...
]
Ronald van Kuijk commented on JBPM-2720:
----------------------------------------
Yep, this is because the executions that did not arrive in the join yet are not ended.
This is a separate issue since I think they should be ended, but cannot for e.g.
tasks/states with a timer on a transition.
This specific issue can be solved by solving the previous statement or be solved by
changing the 'isComplete' method in the join.
Question is: what should be the default behaviour of a join... and concurrent executions
that did not arrive in the join or not? Or should we add another attribute on the join
(e.g. called 'end-concurrent' with values of 'true' and 'false'.
Multiplicity attribute in join doesn't work properly
----------------------------------------------------
Key: JBPM-2720
URL:
https://jira.jboss.org/jira/browse/JBPM-2720
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jBPM 4.3
Reporter: Koen Aers
Fix For: jBPM 4.x
The join activity implementation ends the executions that have arrived in the join. If
the multiplicity attribute is set and the needed amount of executions is reached a second
time, the join executes a second time.
--
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