Comments on: jbpm deployer – Status and Sourcecode

By: Bernd Rücker

Bernd Rücker — Thu, 09 Feb 2012 12:55:00 +0000

Since this is still used out there in Enterprise environments and I discuss that topic from time to time, I wanted to add, that the sketched deployer has one flaw: Since is compares the process definition if a new definition has to be deployed, it always deploys multiple times if you run it in a cluster and restart the nodes simultaneously. The workaround is easy: Don’t start the nodes simultaneously

By: Bernd Rücker

Bernd Rücker — Thu, 09 Feb 2012 11:30:00 +0000

Jut a short addition, since I reused the code myself in another project and had to think about that for a moment. And a good article should comply to the principle: “Don’t make me think!”

The mentioned interface “SwistecJbpmDeployerMBean” added two methods (getProcessClassloder & getProcessClassloaderInformation), but the important thing is, that is extends the JBoss SubDeployerMBean, otherwise the deployer doesn’t start up!

So it looks like this:
public interface SwistecJbpmDeployerMBean extends SubDeployerMBean {
…
}

By: Mick

Mick — Thu, 09 Feb 2012 09:41:00 +0000

Thanks. Very useful post.
Works fine with jboss-soa.
Just packaged as par.deploy.sar and put under /deploy