[
https://jira.jboss.org/browse/JBPM-2414?page=com.atlassian.jira.plugin.sy...
]
Maciej Swiderski commented on JBPM-2414:
----------------------------------------
First of all, Tim, huge thanks for great testing!
I think I got it. It looks like it is caused by order of the operations. Since task is
skipped after execution is removed from its parent - and this is operation on persistent
list. Most likely since it was removed from persistent collection, hibernate decided to
mark this entity as deleted so it could not load it again when fetching the task.
Please find new patch that changes the order and fixes your test
(JBPM-2414-multi-tasks-left.patch)
Tim, please confirm that it works properly for your tests as well. If no one has any
objection I will commit this change.
foreach activity
----------------
Key: JBPM-2414
URL:
https://jira.jboss.org/browse/JBPM-2414
Project: jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Runtime Engine
Reporter: Tom Baeyens
Assignee: Maciej Swiderski
Priority: Optional
Fix For: jBPM 4.4
Attachments: JBPM-2414-2010-05-25.patch, JBPM-2414-20100609-ext.patch,
jbpm-2414-20100609.patch, JBPM-2414-20100616.patch, JBPM-2414-20100621-TEST.patch,
JBPM-2414-doc_and_example.patch, JBPM-2414.patch, mylyn-context.zip, mylyn-context.zip
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
for starters, this might be realized in incubation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira