I am also confused by the use of the term "concurrent" with the fork and join. Concurrent means "occurring or operating at the same time", which is not the case here. Having to manually enhance jBPM to get it to run concurrent processes asynchronously seems odd. I would think this would be the default behavior.
I understand what it is doing, but it is confusing. The documentation in regards to fork and join should spell this out. It would have saved me 4 hours of scratching my head, trying to figure out what is going on... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3911060#3911060 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3911060 ------------------------------------------------------- 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://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
