jbpm supports change of worflow version?

[pedrosacosta]

Let's suppose that i have an application that's running an workflow version1. Now, i modified my workflow, and it calls workflow version 2.
So, applications that has been running version 1, and not finished yet, shouldn't be confronted with the version 2.

Does jbpm supports this kind of examples? If so, how?

Thanks,
Pedro

[pedrosacosta]

And jboss solves the problem of a process versioning explained above, mixed with a server that blows up (view post: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=73486) ?

Thanks.

[pedrosacosta]

In last thread, what i want to tell is, suppose i replace a wf version 1 with the version 2, and the server shuts down. When i restart the server, suppose that the wf version2 wasn't deployed. The server try to deploy again wf version2 automatically?

Thanks

[kukeltje]

First of all,you do not replace it, you add a new version. All currently running processinstances of version 1 will still run according to version 1. New ones will run according to version 2

The default deployment does not exhibit this behaviour afaik, at least I've nevere seen/heard of it. The server does not do the deploymentcompletely by itself. Unless you've written some code that looks in a dir and deploys everything that is in there. If the deployment then failes and the files stays there, it could be that your code will try to deploy it over and over again.