processdefinition and sub-process - autoupdate

[dhartford]

Hi all,
I'm using the jbpm-console, so this may only be related to that webapp.

When I deploy a 'parent' processDefinition with a sub-process, it works fine. When I update the sub-process, it looks like the 'parent' process only continues to use the last-known-good sub-process from when it was last deployed.

This is fine by default, but would be nice to have an attribute to 'alwaysUseMostRecent' version of the sub-process, or on the flip side 'LastGoodSubProcessVersion' to true/false to keep the above described behaviour. I understand there exists a version attribute, but would be easier to have the jbpm understand the intent instead of always manually changing the version number.

thanks,
-D

[dhartford]

darn, forgot versions:

jbpm 3.2Alpha2

JEMS-installed Jboss 4.0.5GA w/ EJB3 profile

[kukeltje]

search the jira. afaik it is a known request

[kukeltje]

search the jira. afaik it is a known request

[kukeltje]

sorry.....

[jainer]

Hi

deploy first the subprocess and then deploy the parent process, it works fine, it don't matter which of both you update.

jainer e.

[avbentem]

"jainer" wrote:
deploy first the subprocess and then deploy the parent process, it works fine, it don't matter which of both you update.

You may be right, but that's not what I remember. Furthermore, I know this is an old post but just for the sake of the archives: at the time of writing this (but probably since some earlier date) one can specifically tell jBPM to always take the latest version:

<process-state name="My sub process">
 <sub-process name="mySubProcess" binding="late"/>
 <transition name="end" to="End"></transition>
</process-state>

Arjan.