jBPM does nothing to avoid the conflict in this case. When the first of any pooled actors 'takes' the task, it should be moved to his own tasklist and out of the pooled list. The task can return to the pooled list by setting the actorid of the task to null. During the process of doing so, the client application should perform the proper locking on the process instance to avoid conflicts.
Regards, Koen View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3928417#3928417 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3928417 ------------------------------------------------------- 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
