protected void init() {
Services.clear();
logConfiguration();
updateSchema();
initProcessEngineConfiguration();
initProcessEngine();
initDeployer();
}
protected void initProcessEngineConfiguration() {
// obtain a configuration form the factory
ProcessEngineConfigurationFactory configurationFactory =
Services.getService(ProcessEngineConfigurationFactory.class);
configurationFactory.setProcessEngineController(this);
processEngineConfiguration = configurationFactory.getProcessEngineConfiguration();
processEngineConfiguration.setProcessEngineName(processEngineName);
processEngineConfiguration.setDataSourceJndiName(datasourceJndiName);
processEngineConfiguration.setJobExecutorActivate(activateJobExecutor);
// disable Activiti schema mechanism complety, it should not even check anything
// we do this on our own, and at least https://jira.codehaus.org/browse/ACT-1062 makes problems
// with schema prefixes of multiple engines
processEngineConfiguration.setDatabaseSchemaUpdate("fox");
if (databaseTablePrefix != null) {
processEngineConfiguration.setDatabaseTablePrefix(databaseTablePrefix);
}
processEngineConfiguration.setDbIdentityUsed(isIdentityUsed);
processEngineConfiguration.setHistory(history);
}
