[jboss-jira] [JBoss JIRA] Commented: (JBPM-708) Version control of the process definition

[Arjan van Bentem (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBPM-708?page=comments#action_12355796 ] 
            
Arjan van Bentem commented on JBPM-708:
---------------------------------------

> it's the user's code that should call the, jbpmContext.deployProcessDefinition()

Just for the archives:

In Seam, org.jboss.seam.core.Jbpm#installProcessDefinitions() is called each time JBoss AS is started. So, if the Seam (exploded) EAR holds a process definition in components.xml, then an additional copy is inserted in the database at each start of JBoss AS. 

Apparently, for Seam this is considered a developers tool:

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

Of course, it's not a jBPM issue, and may not even be a Seam issue, but currently Seam does not seem to provide any other built-in means to deploy a process.

> 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: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira