Koen, I don't believe this is a reason to ditch jBPM :-) It just helps to know the limitations of the tools you're using.
It would however be interesting to know if the jBPM Team accepts true concurrency as a problem. I'm not asking for a solution right now, I just want to know your position. JMS and MDBs will not solve all problems connected to this topic. (I can provide a few examples if needed, but there are obvious ones in this thread already.) And if we're strechting jBPM (or maybe Hibernate) to the limit, hey it's positive that we can even discuss this problem. I'm hooking up with a leagcy system that doesn't even support transactions in some cases. No transactions, no problems... except for the occasionally lost document :-) Now we know the limits and will work with what we've got (at least I will). Have a nice "3. Advent" (any politically correct Americans in this forum? Then sorry. Happy "two weeks before winter holiday weekend") Rainer View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3911935#3911935 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3911935 ------------------------------------------------------- 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
