View RSS Feed

jBPM

Process Versioning

Rate this Entry
by , 04-27-2012 at 05:50 PM (722 Views)
Process instances always execute on the same process definition as that in which they were started. However, the JBPM allows multiple process definitions of the same name to co-exist in the database. Typically, a process instance is started in the latest version available at that time and it will keep on executing in that same process definition for its complete lifetime. When a newer version is deployed, newly created instances will be started in the newest version, while older process instances keep on executing in the older process definitions.

If the process includes references to Java classes, these can be made available to the JBPM runtime environment in one of two ways:

  • by making sure these classes are visible to the JBPM class-loader.
  • To do so, put the delegation classes in a .jar file "next to" jbpm-jpdl.jar so that all of the process definitions will see that class file. The Java classes can also be included in the process archive. When you include your delegation classes in the process archive (and they are not visible to the jbpm classloader), the JBPM will also version these classes inside the process definition.

Submit "Process Versioning" to Facebook Submit "Process Versioning" to Digg Submit "Process Versioning" to del.icio.us Submit "Process Versioning" to StumbleUpon Submit "Process Versioning" to Google

Categories
jBPM Process

Comments