Issak, I have looked at the issue. You could call it a bug, but there is a reason why this problem appears. To understand it properly, you should have a look for yourself in the implementation of the class org.jbpm.identity.assignment.ExpressionAssignmentHandler. You will see there that the resolveNext method indeed returns the first entity in the set of members it finds. It would be ok to return a set of actorIds if this member expression was the last of the chain, but if this is not the last and there are multiple entities returned, it is impossible to resolve the next part of the expression chain. The implementation will not change shortly. If you would like such a thing to be added, enter a JIRA issue for it. Keep in mind that the syntax would have to change slightly (perhaps introducing a 'members()' function that can only be used as the last part of the expression chain. Alternatively, you could implement a custom assignment handler that provides this kind of behaviour (it is not really that difficult to implement) and we will gladly look at your solution to integrate it if you are willing to contribute.
Regards, Koen View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3921811#3921811 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3921811 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
