2 Replies Latest reply on May 1, 2006 2:14 PM by icyjamie

subprocesses linked to superprocess in deploy time - not in

akakunin Apr 27, 2006 11:13 AM

Hello! I found think I'm not sure working correctly in jBPM:

jBPM Process Definition has process-state node for connecting some subprocess to main superprocess. In this node you can specify process name and process version - but if version is not specified - it gets last version.

Problem is that it "get" this last version during process deploying time - not during process execution (starting) time.

For example I have process 1 with process-state node. This node points to process2 without any version, so, last version should be used.

OK, I have in my system process2 version 1 and I'm deploying process1. If I will start process1 it, finally will start process2 version 1 - it is ok.

But then I can deploy new version of process2 - version 2. Of course I want in whole my system do use it instead of old version.

But process-state node in process1 still points to version 1- if I will start process1 it will finally start process2 version 1 - but not the last version 2...

It is special feature you it will be changed sometimes later? Should I report bug into JIRA?

1. Re: subprocesses linked to superprocess in deploy time - not

koen.aers Apr 30, 2006 10:53 AM (in response to akakunin)

Alexey,

To my surprise, this is AFAICS indeed the current behaviour of the engine. So if you want this changed you can report a change request in JIRA. Make sure you refer to this thread. Maybe this should be a configurable option:
--> always last version
--> always current version
--> always some specific anterior version

Regards,
Koen
Actions
2. Re: subprocesses linked to superprocess in deploy time - not

icyjamie May 1, 2006 2:14 PM (in response to akakunin)

I feel neglected :-)
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=80727

I think that, if you can map it in hibernate, it will be fairly easy. You have to tell hibernate to always fetch the latest version (this may be difficult, but you could have a "latest version" mapping, based on a (name,process definition) pair which maps to latest the process definition).
Otherwise, the ProcessState node will have to have a reference to the GraphSession for looking up the latest definition, which may be not desired for the nodes (having a session, that is).
Actions

Go to original post