Again, don't use jBPM as a thread scheduler. Use it as a BPM engine and all will be fine. What can we do? Should we not use the word 'fork' and 'join' because there could be some confusion? Then you could argue about the word 'process'. For some of us this means a bunch of instructions running on a processor, for others it means a business procedure. A fork is a notational element in JPDL, borrowed from UML activity diagrams. As in UML activity diagrams it denotes a split in the execution of a (business) process into two or more paths of execution that may happen in parallel. The runtime engine of jBPM creates two child tokens corresponding to these paths of execution. These child tokens can be signalled independently, but of course only if they end up in a wait state somewhere between the fork and the join. If there is no wait state in between then calculation will be deterministic and there will be no real parallelism.
Regards, Koen View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3911120#3911120 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3911120 ------------------------------------------------------- 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
