As an outsider using jBPM and trying to get it ready for production to run our batch processes, it has been throwing me some curve balls.
Don't get me wrong here, I like jBPM and picked it from a field of other BPM systems (osworkflow, wfmopen, shark, openwfe, etc...) I do look at stuff with a "simpleton's" view of the world, but it has frustrated me in two areas: 1. I expected it automatically persist state whenever a state chage occurs. Say what you will, but my expectation of BPM software that claims to be persistent should do this for you. I shouldn't have to do anything to make this work. I solved this problem by passing around a transient variable with a sychronized transaction that I commited and rebegan at each step, but I don't feel I should have had to do this. 2. I expected parallel processing with a fork. If you have to put a process into a wait state to cause parallel activity, it doesn't feel right. What if intel released a processor that they said allowed concurrent processing but then said "oh, it really doesn't do this unless your code helps us". Enough ranting. I will play with it today to figure out a workable solution in a non-managed environment (jetty). I just wish I didn't have to and could work on my process/job management screens instead. Sean View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3911165#3911165 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3911165 ------------------------------------------------------- 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
