]
Thomas Diesler updated JBPM-1029:
---------------------------------
Assignee: (was: Tom Baeyens)
calling getGroupTaskList results in 4N queries being made to the
database
-------------------------------------------------------------------------
Key: JBPM-1029
URL:
http://jira.jboss.com/jira/browse/JBPM-1029
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.1
Reporter: David Sheth
In the seam 2.0.0.Beta 1 dvdstore example, which uses jbpm-jpdl 3.2.1, one of the admin
pages lists all the tasks assigned to the group of the admin, allowing the admin to assign
one of the tasks to him or herself. In this page, a task represents an order placed in the
store.
Each time a new order is placed in the store, the number of tasks on that admin page goes
up by one, as would be expected. However, the number of queries used render the page of
tasks goes up by 4 each time a new order is placed.
This seems bad. I asked about this in the seam forum, and got this back from Gavin:
--begin quote
AFAIK, this is a jBPM question, not a Seam question, unless you have evidence otherwise.
--end quote
The specific bit of code in the seam bpm libs that is being called is :
return ManagedJbpmContext.instance()
.getGroupTaskList( new ArrayList( Actor.instance().getGroupActorIds() ) );
which is basically just calling getGroupTaskList on an org.jbpm.JbpmContext instance.
Reference to the post in the seam forum:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=114668
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: