Wait, I think I actually get it.
You're saying that since the value of the actorId is pretty much disconnected from reality, I can use any arbitrary string as the actorId, which would mean using the group name.
And as long as I can figure out what the group name is when assigning AND when querying, I can do it however I like.
When you were saying "group" I was thinking JBPM identity group, not my-own-custom-group.
Sorry for being thick headed about this. In my defense, I've been on pain medication :)
Thanks for the help.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223094#4223094
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223094
1: no
assign(Assignable assignable, ExecutionContext executionContext) {
| // do some stuff to dynamically figure out what group to assign to
| assignable.setPooledActors(new String[] { "my-dynamic-group"});
| }
|
Assign to the group NAME, not use an expression
2: Why is this such a problem? ANY decent I&AM solution has a way to decide which groups a user belong to....
as mentioned multiple times in this topic and other ones... for the engine any string you put in the pooled actors is just a string.... without meaning. You give the meaning to it yourself. That is the nice thing wich makes it flexible
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223087#4223087
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223087
