-
Bug Report
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
Currently you have to use a process engine plugin to disable script engine caching:
package my.custom.process.engine.plugin; import org.camunda.bpm.engine.impl.cfg.AbstractProcessEnginePlugin; import org.camunda.bpm.engine.impl.cfg.ProcessEngineConfigurationImpl; /** * Created by hawky4s on 22.06.15. */ public class DisableScriptEngineCacheProcessEnginePlugin extends AbstractProcessEnginePlugin { @Override public void postInit(ProcessEngineConfigurationImpl processEngineConfiguration) { System.out.println("Disabling script engine caching for " + processEngineConfiguration.getProcessEngineName()); processEngineConfiguration.getScriptingEngines().setEnableScriptEngineCaching(false); } }
This fix is included in the following commit:
https://github.com/camunda/camunda-bpm-platform/commit/1f950d4036556d8c9790787a9cd71c7721e614f1