Hi Elmo, just a thought: wouldn't it be worth the effort to implement migration classes?
What I am suggesting is not to change existing process defintions but to define new, changed processes, define a migration class that gets and terminates all process instances of the old process definition and 're-starts' the process instances at the correct point in the new process. The default migration class would map nodes to nodes etc. and you would only have to take care of the complicated stuff that comes up in specific processes and cannot be genrically handled. This isn't trivial but should be worth it, if this happens more than once every other year. (I once hacked a jBPM 2.0 DB to change a process definition and the instances. It wasn't fun and I would have implemented what I described above, but we had a pretty panicy business side that wanted changes 'NOW'.) Other advantages would be data integrity etc. Happy New Year! Rainer View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3915090#3915090 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3915090 ------------------------------------------------------- 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
