Sean, 

As stated multiple times, you should obtain the async behaviour as it is 
specified in multiple good books on integration. Use asynchronous messaging, 
use JMS. There is a simple mechanism of async behaviour included out of the 
box. This is indeed not sufficient for real concurrent behaviour. But there is 
absolutely no need to mess with the transactional alignment of the engine 
execution algorithm : send a message to a queue when entering a state, consume 
it in an MDB, have the MDB signal the token to move it out from the state when 
the work is done. The database will synchronize acces and make sure there is no 
inconsistency. All other solutions are awkward, cumbersome or whatever else you 
may call them.

Regards,
Koen

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3911923#3911923

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3911923


-------------------------------------------------------
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

Reply via email to