[jboss-dev-forums] [Design of JBoss jBPM] - Need for database compatibility between jBPM versions

[thomas.diesler@jboss.com]

In 

http://www.jboss.com/index.html?module=bb&op=viewtopic&t=138168

I state

anonymous wrote : 
  | Database layout is considered implementation detail that might change between minor versions. 
  | 

This is based on my understanding that a process definition is an immutable entity, which is defined in XML.

The state of running processes is persisted in the database. For many a reason It cannot be expected that jBPM can be updated for running proccess. If this feature is required we need to see this reflected in the test suite. In other words, as long as there are no automated tests that verify that an update of jBPM from version X to version Y for a non trivial set of running processes - this feature is not there.

The API will support 


  | ProcessEngine.prepareForShutdown()
  | 

This will allow processes to terminate, while others cannot start. A user is expected to setup a new instance of jBPM version Y that can receive new process requests. 

>From that perspective, it is unnecessary and not even desired to provide backwards compatibility for database layout.

 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161691#4161691

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161691