[rules-users] [Drools Flow 5.1] Updating a process definition -> Proceed updates running processes

[anton.litvinenko]

Esteban, please explain if a process cannot be updated (and one has to deploy
a new process with a different id whenever he/she changes the process
definition), then what does the second part of the
http://downloads.jboss.com/drools/docs/5.1.1.34858.FINAL/drools-flow/html/ch04.html#d0e1514
mean?

Quoting the doc:
"By default, Drools Flow uses the proceed approach, meaning that multiple
versions of the same process can be deployed, but existing process instances
will simply continue executing based on the process definition that was used
when starting the process instance."

But if the id is different then, these are different processes and Drools
Flow simply doesn't know that they are same processes under different names.
So, the "proceed" behavior is met trivially - there is not even possible for
2 different versions of the same process to exist at the same time? Do I
understand correctly that for Drools Flow 2 processes are the same when it
they have the same id?

So, basically, if I use Guvnor and someone uploads a new version of the
process and compiles it, then my application automatically picks up the
updated version even for currently running processes (stopped at
asynchronous step) is that correct? And if I want existing processes to
continue then I need to use a different id for update process (and hence
re-configure the whole app to start processes based on new id) which kind of
a kills all the Guvnor idea.

It seems like I am not understanding something. I would be very thankful, if
someone could explain to me, what I am getting wrong.

Thanks!

--
View this message in context: http://drools.46999.n3.nabble.com/Drools-Flow-5-1-Updating-a-process-definition-Proceed-updates-running-processes-tp2928103p2985647.html
Sent from the Drools: User forum mailing list archive at Nabble.com.