[jbpm-issues] [JBoss JIRA] Commented: (JBPM-2414) foreach activity

[ https://jira.jboss.org/jira/browse/JBPM-2414?page=com.atlassian.jira.plug... ] Ronald van Kuijk commented on JBPM-2414: ---------------------------------------- What I have implemented for now: <for-each name="fork" vars="#{myCollection}" var="item"> <transition to="myTask" name="to_task"/> </for-each> <task name="myTask"> <transition to="join" name="to_join"/> </task> <join name="join"> <transition to="myTask" name="to_end"/> </join> What this does is create new executions for each element in a collection (set, list, collection, array) and put a variable with the name 'item' that in a local scope for the execution. In e.g. the task you can do whatever you want with that variable.... Assignments, do things in event-listeners whatever.... Limitations: - it can only have one outgoing transition - A corresponding join with one incomming transition is needed - Complex nesting things between this for-each and join can and most likely will result in strange behaviour (although I think this is very acceptable) Additions: - The join now accept an EL for multiplicity. A Long/Integer, String (that will be parsed runtime) and a collection (size will be determined runtime). Things like 70% of the created executions has to be passed before it will continue can work now... cool isn't it? One thing I maybe like to change is not call it 'foreach/for-each' but put it in the fork... This makes it visible in the designer, *now*. Comments? After that, I will add the patches here. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira