I want to know the idea behind creating a actorId and a pooledActorId.
Technically if we go into the code, I dont see why we need an actorId.
I can just make use of pooledActorIds.
Say for example
I have taskInstance.setActorId("bert"), i can get the tasks assigned to bert by
saying taskMgmtSession.findTaskInstances("bert").
I can also have something like taskInstance.setPooledActors(new
String[]{"bert"}), and can get the tasks assigned to bert by saying
taskMgmtSession.findPooledTaskInstances("bert"). Pooled actors is more
useful, because I can have more than one user or group. Why the notion
of actorId in taskInstance?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3948724#3948724
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3948724
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
