Process modification

[Mattanja Kern <ma...@kernetics.de>]

Hi,

I need a short confirmation (or clarification) on this process modification issue:

Is it correct that when updating (i.e. redeploying) a process with the same name, all running instances of the current process will be destroyed?
(in implementations of ProcessDAO.deleteProcessAndRoutes)

So the only way to "upgrade" a long-running process with active instances that should not get lost would be to deploy the new version with a different name - correct?

I am currently working on my diploma thesis at Uni Stuttgart about modifying running BPEL-Instances and will hopefully implement a prototype of a modification service based on events.

Regards,
Mattanja

Re: Process modification

[Tammo van Lessen <tv...@gmail.com>]

Hi Mattanja,

Mattanja Kern wrote:
> Is it correct that when updating (i.e. redeploying) a process with
> the same name, all running instances of the current process will be
> destroyed? (in implementations of ProcessDAO.deleteProcessAndRoutes)

true.

> So the only way to "upgrade" a long-running process with active
> instances that should not get lost would be to deploy the new version
> with a different name - correct?

That's even conceptually the only way to do that as the engine cannot
guess how to continue a process instance that has been started with
process version 1 with an updated model. Thus you need to deploy several
versions of the same process (i.e. with the same QName (in directories
like HelloWorld-1, HelloWorld-2, etc. for hotdeployments or with the
same bundle name when deployed remotely).

> I am currently working on my diploma thesis at Uni Stuttgart about
> modifying running BPEL-Instances and will hopefully implement a
> prototype of a modification service based on events.

Care to elaborate what a "modification service based on events" is?

Best,
  Tammo

-- 
Tammo van Lessen - http://www.taval.de