Well this is the problem. You cannot have concurrent updates of processinstances, so you will always have to lock them. This is true in normal concurrent programming as well. If one thread updates the process context and doesn't want the other thread to mess up his updates it has to use a monitor that prevents the other thread from updating the process context (the synchronized block in Java). In our case the process context (processinstance) is in the database and we use regular database locking techniques to obtain the isolation (lockProcessInstance). If you do need something else, I would conclude jBPM is not the best solution.
Regards, Koen View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3911919#3911919 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3911919 ------------------------------------------------------- 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
