]
Peter Brewer commented on JBPM-708:
-----------------------------------
I've added an enhancement that uses source control prevent unnecessary redeployment.
Have a look at:
Version control of the process definition
-----------------------------------------
Key: JBPM-708
URL:
http://jira.jboss.com/jira/browse/JBPM-708
Project: JBoss jBPM
Issue Type: Feature Request
Components: Core Engine
Affects Versions: jBPM 3.1.1
Reporter: Aravind Kumar
Assigned To: Tom Baeyens
When working with jBPM in developement environment, there is no control over the version
of the process-definition.
Each time the server is restarted, a new version is deployed.
The work around that I did:
<boolean name="update-definition" value="false"/>
this tag is included in the jbpm.cfg.xml
& a check at JbpmContext.java:
public void deployProcessDefinition(ProcessDefinition processDefinition) {
if(JbpmConfiguration.Configs.getBoolean("update-definition")) {
getGraphSession().deployProcessDefinition(processDefinition);
}
}
This works fine for a single process defifnition. In case, there are multiple process
definitions and some needs to be updates and some need not be.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: