I think I've identified a broader issue than that listed above. I don't think the current code is built to support reassignment of SwimlaneInstance pooledActors (though reassigning the actor seems to work fine).
In support of that statement--if a TaskInstance does not have any pooledActors itself, it will try to return it's SwimlaneInstance's pooledActors; however, if assignments to the SwimlaneInstance's pooledActors are made after the TaskInstance has been created, the TaskInstance will (as mentioned) return the pooledActors assigned to the SwimlaneInstance while taskMgmtSession.findPooledTaskInstances(theSamePooledActor) returns nothing (from the jbpm_taskactorpool table).
Another related issue is that calling swimlaneInstance.setPooledActors(pooledActors) doesn't replace the pooledActors already in the database, it adds to them.
Unless someone steps up to make the argument that we shouldn't be reassigning a SwimlaneInstance's PooledActors anyway, I'll create a JIRA issue on this and label it as a bug (since the method calls are already there, and actor reassignment is functional).
Personally, this functionallity is fairly important to my own applications.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3897485#3897485
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3897485