This is a known feature, a consequence of the graph traversal technique used in jBPM derived from the classic chain of responsibility pattern (more details in section 4.4 of the user guide).
The biggest advantage of this technique is that it deals neatly with multiple transitions going out of a node, or linked activities within a flow structure. It ensures you can backtrack all the way to the activity with multiple outgoing transitions. Spawning a thread for each transition is an alternative; unfortunately, it is incompatible with JEE deployments. Anyway, a portion of a process that loops hundreds or thousands of times over an activity probably shouldn't be described at the (coarse grained) orchestration level. You'd be better off moving that (fine-grained?) logic to a partner service. Can you describe the use case, please? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3921595#3921595 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3921595 ------------------------------------------------------- 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
