First of all, discussion is certainly good. It is the primary force of open source development, so there is indeed no reason to stop discussing and poining out weaknesses of jBPM. But it is very important that everybody knows they should *not* try to code nodes which mess with the transaction alignment of the engine. It is a bad, very bad way to solve problems, which may, and certainly will, cause major problems. Rollbacks will put the database in an incosistent state. Second, I would be happy to see clearly described use cases for which the use of asynchronous (JMS) messages will not give a solution. If you don't use a solution like this, you will end up implementing your own substitute for this. Third, JMS neither MDB are particular to JBoss, you can use them in any appserver you like. If you have another system of doing asynchronous messaging (your own rolled), jBPM will happily use it if there is a Java API. So I still don't see the point in this whole discussion.
Regards, Koen View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3911948#3911948 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3911948 ------------------------------------------------------- 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
