I suppose you will need to implement it by yourself and it will be very big job..., because I think it is not possible to implement such functionality for general process definitions.
As I understand concept of jBPM different versions of one process definition - are actually different process definitions only linked by same name. So, new version of process definition may have completelly another structure. For already running process you have state - tokens placed in specified nodes, specified tasks assigned to specified swimlanes... but in new process you may have not these nodes, tasks and swimlanes because they was removed... So, rootToken placed in running process in nodeA, but from that node you will continue execution in new process definition? So, I suppose for general case it is not possible to implement. If you have sume restirctions for versions (for example nodes should not be removed in new version - but only added, node names should not be changed and so on) you will able to implement some sort of switching to new version by yourself - but only specially for your cases View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3943780#3943780 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3943780 ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
