topic SpringProcessEngineConfiguration - autodeploy in Alfresco Archive

SpringProcessEngineConfiguration - autodeploy

chris889 — Tue, 17 May 2011 06:09:28 GMT

Hi,Is there a built in way to auto-deploy bpmn resources only if there has been a change in the bmn20.xml file? Setting the deploymentResources property of the SpringProcessEngineConfiguration bean seems to deploy everytime the spring container is started.brChristoph

Re: SpringProcessEngineConfiguration - autodeploy

trademak — Tue, 17 May 2011 07:51:11 GMT

Hi,

No, there's no feature built-in yet to listen for changes in the bpmn20.xml.
You could however do this with the Camel or Mule ESB integration. Or implement a file listener yourself.

Best regards,

Re: SpringProcessEngineConfiguration - autodeploy

chris889 — Tue, 17 May 2011 08:02:28 GMT

Thanks for the quick reply. I just wrote my own deployer bean, you can find it here for reference: http://pastebin.com/JU4J0rCr.

Re: SpringProcessEngineConfiguration - autodeploy

trademak — Tue, 17 May 2011 09:19:41 GMT

Okay great!,

Best regards,

Re: SpringProcessEngineConfiguration - autodeploy

frankee787 — Wed, 10 Aug 2011 13:03:36 GMT

Isnt deploymentResources supposed to take care of this ? Every time I run it keep deploying again. As per the documentation

Spring integration also has a special feature for deploying resources. In the process engine configuration, you can specify a set of resources. When the process engine is created, all those resources will be scanned and deployed. There is filtering in place that prevents duplicate deployments. Only when the resources actually have changed, will new deployments be deployed to the Activiti DB. This makes sense in a lot of use case, where the Spring container is rebooted often (eg testing).

it shouldnt be deploying it again. Am I missing something ?

Re: SpringProcessEngineConfiguration - autodeploy

jbarrez — Thu, 11 Aug 2011 09:43:11 GMT

The check is done compring the xml bpmn 2.0 files with each other.
Only when something has changed it such a file, the processes are redeployed.

Re: SpringProcessEngineConfiguration - autodeploy

frankee787 — Thu, 11 Aug 2011 09:54:26 GMT

Just to clarify my understanding.So if I were to re-run my test cases would it keep deploying a new version?

For eg:
Lets say I run my test at 10:00 for the first time. Now the xml bpmn 2.0 has timestamp of 10:00 in the file system. Hence it will be deployed and will be registered as a new version in the Activit DB.

Lets say now I run my test at 10:05 for the second time. Now the xml bpmn 2.0 has still timestamp of 10:00 in the file system.

Will it be re-deployed now ?

Best Regards,
Franklin

Re: SpringProcessEngineConfiguration - autodeploy

frederikherema1 — Thu, 11 Aug 2011 13:51:00 GMT

It compares based on the content of the file (the inputStream sent to the DB) not the actual file-metadata.

Re: SpringProcessEngineConfiguration - autodeploy

frankee787 — Thu, 11 Aug 2011 17:08:31 GMT

Thanks for the clarification.

However, each time I bootstrap the spring context the a new version is being deployed in the Activit DB. I am sure, neither the metadata nor the content of the file is changing.

Still the process is being redeployed. Any one got this working ?

Regards,
Franklin

Re: SpringProcessEngineConfiguration - autodeploy

st_patriick — Thu, 11 Aug 2011 18:21:08 GMT

There is a bug in this feature. See (and vote for): http://jira.codehaus.org/browse/ACT-736

Re: SpringProcessEngineConfiguration - autodeploy

frankee787 — Thu, 11 Aug 2011 20:03:32 GMT

Hmmm…thats pretty disappointing. Does it really fail only in Oracle? Cause mine is MySQL and still it fails.

Re: SpringProcessEngineConfiguration - autodeploy

frankee787 — Mon, 17 Oct 2011 07:35:11 GMT

Thanks for the quick reply. I just wrote my own deployer bean, you can find it here for reference: http://pastebin.com/JU4J0rCr.

How are you instantiating the bean in spring context?

Regards,
Franklin

Re: SpringProcessEngineConfiguration - autodeploy

chris889 — Mon, 17 Oct 2011 07:39:59 GMT

Well, I just reference it in my spring applicationcontext.xml configuration file (i.e. <bean class="org.this.is.my.namespace.WorkflowDeployer"/>)

Re: SpringProcessEngineConfiguration - autodeploy

frankee787 — Mon, 17 Oct 2011 08:01:50 GMT

For me it gives an error as follows



[2011-10-17 11:14:33,062] org.springframework.web.context.ContextLoader - Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'workflowDeployer' defined in file [C:\ApacheTomcat\apache-tomcat-6.0.28\webapps\WEB-INF\classes\activiti.cfg.xml]: Invocation of init method failed; nested exception is org.springframework.beans.FatalBeanException: Missing property: category
 at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1420)
 at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)
 at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
 at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:295)

Re: SpringProcessEngineConfiguration - autodeploy

sanjiv — Fri, 12 Jul 2013 14:36:25 GMT

Is this feature still broken? Spring "deploymentResources" setting results in a new deployment in the Activiti tables each time the app is restarted. http://jira.codehaus.org/browse/ACT-736 is marked fixed in Activiti Engine 5.9 in Feb 2012. Which version of Activiti does this correspond to? I'm using v5.12.1 and I'm facing the same issue.

Thanks,
Sanjiv

Re: SpringProcessEngineConfiguration - autodeploy

frederikherema1 — Wed, 17 Jul 2013 10:43:00 GMT

We have a test for this: org.activiti.spring.test.autodeployment.SpringAutoDeployTest.testNoRedeploymentForSpringContainerRestart, which runs green on our QA (against H2).

 public void testNoRedeploymentForSpringContainerRestart() throws Exception {
    createAppContext(CTX_PATH);
    DeploymentQuery deploymentQuery = repositoryService.createDeploymentQuery();
    assertEquals(1, deploymentQuery.count());
    ProcessDefinitionQuery processDefinitionQuery = repositoryService.createProcessDefinitionQuery();
    assertEquals(3, processDefinitionQuery.count());
    
    // Creating a new app context with same resources doesn't lead to more deployments
    new ClassPathXmlApplicationContext(CTX_NO_DROP_PATH);
    assertEquals(1, deploymentQuery.count());
    assertEquals(3, processDefinitionQuery.count());
  }

Actual code that checks the duplicates:


if ( deploymentBuilder.isDuplicateFilterEnabled() ) {
      DeploymentEntity existingDeployment = Context
        .getCommandContext()
        .getDeploymentEntityManager()
        .findLatestDeploymentByName(deployment.getName());
      
      if ( (existingDeployment!=null)
           && !deploymentsDiffer(deployment, existingDeployment)) {
        return existingDeployment;
      }

Deployment is looked up by name (in this case, SpringAutoDeployment) and all non-generated resources are checked to see if they differ (byte-level). If they differ, a new deployment is created.

What DB are you on? only thing I can think of is that the bytes returned from the database are a bit different than the bytes from the actual files on the hard disk (maybe encoding?).