It looks like it is a jbpm feature and goes by versioning mechanism. I see the
following in the jbpm jpdl reference at
http://www.jboss.com/products/jbpm/docs/jpdl
How do I avoid versioning and keep the same process definition unless something
has really changed in the process definition file? Any help deeply appreciated.
IN my scenario, the server may be brought up and down multiple times and every
time this is done, I will lose all contexts from previous actions, unless I
store the processDefinition Id in a user database.
-----------
Versioning mechanism
Basically, the versioning mechanism of jBpm comes down to the following
principles :
* every time a process archive is deployed, a new process definition is
created in the jBpm database
* at deployment, jBpm assigns a version number to the process definition.
Process archives are considered the same when the name of the process is the
same. To assign the version number, jBpm takes 1 + (the highest version number
of the current process definitions with the same name). Or 1 if it is the first
version. From the jBpm-API you can ask for the latest process definition with a
given name.
* ones a process instance (=one process execution) is started in a given
definition, the process instance will keep on executing within the same
definition till its finished.
* this way every process can start in the latest definition and keeps on
running in the same definition for its complete lifetime.
* note that in jBpm it is even possible to version the programming logic
associated with a process. By including the classes in the process archive,
jBpm will separate the classes per process definition.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131457#4131457
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131457
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user
