Found a workaround
We have process instance (process instance id) so we can also use API:
Collection taskCollection =
processInstance.getTaskMgmtInstance().getTaskInstances();
Then look for the given Actor Id.
We don't have many Task Nodes so this should not cause any performance problem.
Looks like there may be a problem in
getTaskMgmtSession().findTaskInstances("user id") on JbpmContext.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3935283#3935283
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3935283
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
