]
Thomas Diesler reassigned JBPM-1921:
------------------------------------
Assignee: Thomas Diesler
getGroupTaskList(List actorids) behaviour changed
-------------------------------------------------
Key: JBPM-1921
URL:
https://jira.jboss.org/jira/browse/JBPM-1921
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: API
Affects Versions: jBPM 3.3.0 GA
Reporter: Daniel Bremer-Tonn
Assignee: Thomas Diesler
Fix For: jBPM 3.3.1 GA
We migrated from jpdl v3.2.3 to v3.3 and did see some new behaviour for
"JBPMContext.getGroupTaskList(List actorIds)".
Behaviour in V3.2.3: Assigning a task to two pooledActorIds and calling
JBPMContext.getGroupTaskList(List actorIds) with these two pooledActorIds will get you a
list with one TaskInstance.
In v3.3 you will get now a list with two items, which are two references to the same
Taskinstance.
While digging into the code I've found a change in the corresponding hibernate-query
("TaskMgmtSession.findPooledTaskInstancesByActorIds" in
hibernate.queries.hbm.xml). The 3.2.3 version uses the "distinct" keyword, while
the 3.3 one does not.
Since this is some change in behaviour of the method JBPMContext.getGroupTaskList(List
actorIds) either it should be fixed, or if intended should be documented somewhere.
Best regards,
Daniel Bremer-Tonn
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: