jPDL focusses on the state machine / transaction / persistence mechanics of workflow and BPM. And this is definitely different from multithreaded programming.
Lately i have been thinking about it in the context of Graph Oriented Programming (jbpm.org/gop) and i'm starting to be convinced that we could create a new process language for defining multithreaded behaviour: Each node in the graph could be associated with a plain command. A split and merge node could be introduced to spawn (and synchronize) multiple concurrent java threads. No persistence, no transactions, ... It could be done. But i think it is another process language. In a second stage we could think about how to embed a piece of the multithreaded process language in e.g. jPDL... regards, tom. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3924504#3924504 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3924504 ------------------------------------------------------- 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
