Bernd, deploying a new process and migrating is not a feasible option for large, complicated, long running process. When we take a new order, we don't have one process. Under one new order we spawn an order validation process, a credit check process, multiple service processes for each type of service on the order, each service process can spawn various vendor service order processes, etc., etc. Each new order can easily represent 15 processes of various types that are all interwoven together at some level. There is nothing unusual about our business; its typical telecom. In this environment, it is rare that migration is an option. While late binding of subprocesses helps a lot, there are simply times when we must update processes in place. What Tom was proposing greatly helps us do that (what we're going to do anyway) in as safe a way as possible. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053594#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...