org.activiti
Interface ProcessEngine
public interface ProcessEngine
provides access to all the services that expose the BPM and workflow operations.
Typically, there will be only one central ProcessEngine instance needed in a
end-user application. Building a ProcessEngine is done through a
DbProcessEngineBuilder instance and is a costly operation which should be
avoided. For that purpose, it is advised to store it in a static field or
JNDI location (or something similar). This is a thread-safe object, so no
special precautions need to be taken.
- Author:
- Tom Baeyens, Joram Barrez
|
Field Summary |
static java.lang.String |
VERSION
the version of the activiti library |
VERSION
static final java.lang.String VERSION
- the version of the activiti library
- See Also:
- Constant Field Values
getName
java.lang.String getName()
- the name as specified in the 'process.engine.name' property in
the activiti.properties configuration file or in the
The default name for a process engine is 'default
getProcessService
ProcessService getProcessService()
getTaskService
TaskService getTaskService()
getHistoricDataService
HistoricDataService getHistoricDataService()
getIdentityService
IdentityService getIdentityService()
getManagementService
ManagementService getManagementService()
close
void close()
Copyright © 2010 Alfresco. All Rights Reserved.