Hi 'chprvkmr', it's actually quite simple.
Use JMS to spawn a new Thread. To do that give the Message all the information needed (tokenId, expected nodeId - just to be sure, transition to take), send it to a MDB that triggers the transition. The amount of concurrent Threads depends on the configuration of your MDBs. If you're using the SchedulerThread from jBPM and have a look at the source code, you'll see that everything does happen sequentially and even in a single transaction. See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=73234. If you don't want to use the SchredulerThread you'll probably have to roll your own, i.e. start your own Threads. There is a possible problem with concurrent execution. Depending on what aspects of the processInstance you're changing you could get conflicting concurrent changes in the DB. See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=73332. I'm using jBPM 3.0.2 and it works for me. Freeting Rainer View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3910701#3910701 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3910701 ------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
