[jbpm-dev] [Design of JBoss jBPM] - Re: Creatiing new pooled actors for every task instance

[kukeltje]

David,

Deciding assignments at the time of deployment is a totally wrong approach. Things might change while running the process. The pooled actors for a taskinstance might different to another instance although refering to the same swimlane. It certainly does for most of the processes we've created.. So each taskinstance having it's own pooled-actors, or refering to a swimlane is imo the right approach. That using swimlanes does not reduce it, by having e.g. the swimlanes for a processinstance refering to the pooled-actors table might be considered an 'issue' although I'm not to familiar with the internal workings of this part. 

Do you have an example of the number of joins? Since (without looking at the query) my impression is that it is not to bad.  

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4195159#4195159

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4195159