Jesse, Why exactly would you need long transactions? And what do you exactly mean with it? Can you give an example? Normally the transactions in jBPM are not long at all, they only serve to calculate the new state of the process instance after giving one or another token the signal to move on. To make these transactions long running, you would have to develop a node or an action that invokes long running operations. But you have to realize that, as the calculations of the new state are executed in the client thread, this would freeze your client application. The workaround for this is to use asynchronicity, but then (at least for jBPM) you don't have long running transactions anymore.
Regards, Koen View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3930916#3930916 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3930916 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
