]
Sebastian Schneider commented on JBPM-2807:
-------------------------------------------
In my thoughts I have not taken into account backwards compatibility. So it might be a
smoother way to allow this and log a warning instead. In this case this will have to be
changed already in 4.5 IMHO. For me this is an unclean way of working with tasks. So
I'd love to hear if the others think this kind of "backwards compatibility"
is necessary or not.
How would you log the task in this case? With status cancelled or timed out?
A task is put in an unusable state if the execution it belongs to is
signalled
-------------------------------------------------------------------------------
Key: JBPM-2807
URL:
https://jira.jboss.org/jira/browse/JBPM-2807
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jBPM 4.x, jBPM 4.3, jBPM 4.2, jBPM 4.1, jBPM 4.0
Reporter: Ronald van Kuijk
Priority: Minor
Fix For: jBPM 4.x
Original Estimate: 1 day
Remaining Estimate: 1 day
When an execution is signalled, the task belonging to that execution becomes unusable. It
is made 'not-signalling', has no exection (thus cannot be ended, which you would
not want to) but it keeps showing up in the tasklist....
Proposed solution is to have an additional task state (like the 'timeout' that is
introduced). If an execution is signalled, the task is 'cancelled' this is
something completely different then it being completed or any other state....
The behaviour of which transition will be taken will not be different from what it is
now.... A warning will be logged that a execution is signalled and it would be better to
act on the task itself...
Subtasks will/should be treated the same.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: