Avoiding engine restarts for Java class modifications

[jmaru]

Hi,

We are evaluating Activiti for our BPM solution and it looks like a great developer-friendly tool. I noticed a requirement that we need to restart the Process Engine whenever we add or modify any of the Java classes associated with a process/flow (for eg. Java Service task). We don't want to do that since it might mean downtime for our users which would be pretty bad. Are there ways to avoid having to restart the engine? I would love to hear if someone has overcome this requirement or workarounds that people have taken.

Thanks,
Jeegar Maru

[trademak]

Hi,

This is a limitation of the Tomcat environment.
Camunda has built an JBoss 7 extension for Activiti that does exactly what you are looking for. And it's open source.
There you can deploy a new process definition with the classes while the server keeps on running.

Best regards,