3:18 a.m.
Hi,
As you may know, previous releases of JBPM had support for jPDL
processes versioning.
As per the deployment process, the process was serialized as Java
objects into the database as blobs once it was converted as such at
deployment time.
From that time on, every process in execution was linked to it's process
serialization ( the version that was active at that moment ) and subsequent
serializations of newer versions of the same process where versioned and
the new process instances keep track of what version of the process
definition they were linked to. That made very easy the task of updating
process definitions in an application just keeping in mind that previous
process instances will execute by the previous process definition and newer
process instances will follow the latest process definition version.
Now, in JBPM 5.x things don't seem to work that way anymore. Processes
are defined using BPMN 2.0, live in a Drools KnowledgeSession, and seems
there's no support for process definition versioning.
So, how would you solve the problem of having in the same
KnowledgeSession different versions of the same process ( each having it's
bag of process instances attached ) in JBPM 5.x ? Is it that even
possible?. We have a long time running application that has up to 7
different versions of a process and this really is a feature we need.
Seems that one solution would be to have different versions of the
process definition live in the knowledge session bound to different process
names and make your application aware of that when launching new instances
... but that seems more of a workaround ... Is this really the unique
solution for this?
Greets,
Alberto R. Galdo
argaldo(a)gmail.com
7:12 a.m.
I'm not sure if this answers your question but JBPM 5.x does offer process mapping:
http://docs.jboss.org/jbpm/v5.0/userguide/ch03.html#d0e1280
--
Build Smarter Software.
Spantree Technology Group, LLC
813 W Randolph St, Suite 301, Chicago, IL
email: cedric(a)spantree.net (mailto:cedric@spantree.net) | phone: 773.359.3865
(tel:773.359.3865)
On Thursday, October 18, 2012 at 3:18 AM, Alberto R. Galdo wrote:
Hi,
As you may know, previous releases of JBPM had support for jPDL processes versioning.
As per the deployment process, the process was serialized as Java objects into the
database as blobs once it was converted as such at deployment time.
From that time on, every process in execution was linked to it's process
serialization ( the version that was active at that moment ) and subsequent serializations
of newer versions of the same process where versioned and the new process instances keep
track of what version of the process definition they were linked to. That made very easy
the task of updating process definitions in an application just keeping in mind that
previous process instances will execute by the previous process definition and newer
process instances will follow the latest process definition version.
Now, in JBPM 5.x things don't seem to work that way anymore. Processes are defined
using BPMN 2.0, live in a Drools KnowledgeSession, and seems there's no support for
process definition versioning.
So, how would you solve the problem of having in the same KnowledgeSession different
versions of the same process ( each having it's bag of process instances attached ) in
JBPM 5.x ? Is it that even possible?. We have a long time running application that has up
to 7 different versions of a process and this really is a feature we need.
Seems that one solution would be to have different versions of the process definition
live in the knowledge session bound to different process names and make your application
aware of that when launching new instances ... but that seems more of a workaround ... Is
this really the unique solution for this?
Greets,
Alberto R. Galdo
argaldo(a)gmail.com (mailto:argaldo@gmail.com)
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org (mailto:rules-users@lists.jboss.org)
https://lists.jboss.org/mailman/listinfo/rules-users
11:04 a.m.
I did read that in the manual before and that's what I was referring to
with "different versions of the process definition live in the knowledge
session bound to different process names" but what I'm looking for is for
an automated solution and this solution on the JBPM side.
One solution that doesn't upgrades my current process instances to the new
process definition ( that will never be automated as this process is faulty
by definition and needs human intervention given the broad spectrum of use
cases here ) but manages the associations between my current process
instances to the old process definition and starts new process instances
with the new updated process definition.
Something like a BPMN process versioning support feature in JBPM ;-)
Alberto R. Galdo
argaldo(a)gmail.com
On Thu, Oct 18, 2012 at 2:12 PM, Cedric Hurst <cedric(a)spantree.net> wrote:
I'm not sure if this answers your question but JBPM 5.x does
offer
process mapping:
http://docs.jboss.org/jbpm/v5.0/userguide/ch03.html#d0e1280
--
Build Smarter Software.
Spantree Technology Group, LLC
813 W Randolph St, Suite 301, Chicago, IL
email: cedric(a)spantree.net | phone: 773.359.3865
On Thursday, October 18, 2012 at 3:18 AM, Alberto R. Galdo wrote:
Hi,
As you may know, previous releases of JBPM had support for jPDL
processes versioning.
As per the deployment process, the process was serialized as Java
objects into the database as blobs once it was converted as such at
deployment time.
From that time on, every process in execution was linked to it's
process serialization ( the version that was active at that moment ) and
subsequent serializations of newer versions of the same process where
versioned and the new process instances keep track of what version of the
process definition they were linked to. That made very easy the task of
updating process definitions in an application just keeping in mind that
previous process instances will execute by the previous process definition
and newer process instances will follow the latest process definition
version.
Now, in JBPM 5.x things don't seem to work that way anymore. Processes
are defined using BPMN 2.0, live in a Drools KnowledgeSession, and seems
there's no support for process definition versioning.
So, how would you solve the problem of having in the same
KnowledgeSession different versions of the same process ( each having it's
bag of process instances attached ) in JBPM 5.x ? Is it that even
possible?. We have a long time running application that has up to 7
different versions of a process and this really is a feature we need.
Seems that one solution would be to have different versions of the
process definition live in the knowledge session bound to different process
names and make your application aware of that when launching new instances
... but that seems more of a workaround ... Is this really the unique
solution for this?
Greets,
Alberto R. Galdo
argaldo(a)gmail.com
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
4426
days inactive
4426
days old
2 comments
2 participants
participants (2)
-
Alberto R. Galdo -
Cedric Hurst