I think this is a real problem! But in our application we have simply solved that by adding a processVariable for the running version and changed that if we "upate" a process version.
The jbpm-log then keeps track at which time in the process execution the version was changed (and the old and new version number). So we know whats going on... anonymous wrote : starting the new one in the same or matching state How do you do this with jBPM? Some kind of hack to get a process in the state you want? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3917477#3917477 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3917477 ------------------------------------------------------- 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
