Versioning deployments / processes and the remote API in jBPM 6

[clp207]

I'm trying to understand how versioning relates to both deployments and processes in jBPM 6.

In my test scenario, I am building kjars with maven and deploying them to a remote jbpm console running on wildfly. I then add a new deployment unit in the console by specifying the GAV of the artifact. It appears that everytime I update the version of my kjar and create a deployment, a new process definition is created even if the version of the process is the same. Is this the expected behaviour?

My biggest concern is that ito start processes using the remote API, It looks like I need to use the deployment id. However, if my build process updates my kjar version, all remote clients will need to be aware of the deployment version when starting processes. It seems like the client should only need to know process id and maybe process version if they don't want to use the latest version.

Any insight would be greatly appreciated.

[clp207]

Some Updates...

- You can use the remote API to start a process and instead of passing the version for the deployment version, you can pass "latest"

- The deployment version is what seems to really matter since by default you have push a new deployment version every time you deploy. You can override this behaviour, but you can still only update if there are no active instances.

[abhijithumbe]

Hi,

Yes, from jBPM 6.2 onwards we can use 'LATEST' in deploymentId to use latest release of kjar available in the server repository.

jBPM 6.2 dont allow to override artifact.To override artifact you have to pass "-Dorg.kie.override.deploy.enabled=true" while starting server instance.

[clp207]

Is there a way to use maven version ranges in the deployment id?

[abhijithumbe]

As per my understanding we cant use version ranges for deploymentID in java code.Feel free to open feature request for this.