-
Bug
-
Resolution: Done
-
Major
-
jBPM 3.2.7, jBPM 3.2.8
-
None
org.jbpm.command.GetTaskListCommand.execute() throws JbpmPersistenceException if there is no pooled task instances for a given actor even if the actor has personally assigned task instaces.
=====
org.jbpm.persistence.JbpmPersistenceException: couldn't get task instances by ids '[]'
at org.jbpm.db.TaskMgmtSession.findTaskInstancesByIds(TaskMgmtSession.java:204)
at org.jbpm.db.TaskMgmtSession.findPooledTaskInstances(TaskMgmtSession.java:123)
at org.jbpm.JbpmContext.getGroupTaskList(JbpmContext.java:194)
at org.jbpm.command.GetTaskListCommand.execute(GetTaskListCommand.java:54)
at sample.task.ws.TaskSampleWS.test(TaskSampleWS.java:52)
=====
In case of CP01, GetTaskListCommand returns the personal task list without Exception.
This behavior is caused by the change introduced by r4076 in org.jbpm.db.TaskMgmtSession.findTaskInstancesByIds().
r4705
===
public List<TaskInstance> findTaskInstancesByIds(List<Long> taskInstanceIds) {
List<TaskInstance> result;
if (taskInstanceIds.isEmpty())
else {
try
catch (Exception e)
{ handle(e); throw new JbpmException("couldn't get task instances by ids '" + taskInstanceIds + "'", e); } }
return result;
}
===
r4706
===
public List findTaskInstancesByIds(List taskInstanceIds) {
try
catch (HibernateException e)
{ handle(e); throw new JbpmPersistenceException("couldn't get task instances by ids '" + taskInstanceIds + "'", e); } }
===
The change was related to JBPM-2205 and removed the empty check because the method Collections.emptyList() is not supported in jdk1.4. But I think an equivalent empty check should be restored.
- blocks
-
JBPAPP-3112 DVDStore application fails to log in admin user
- Closed
-
JBPAPP-3125 Upgrade Drools and jBpm to versions last used in SOA
- Closed
- relates to
-
JBPM-2205 Restore compatibility with JDK 1.4.2
- Closed