org.camunda.bpm.engine
Interface ProcessEngine
- All Known Implementing Classes:
- ProcessEngineImpl
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
ProcessEngineConfiguration 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, Daniel Meyer
|
Field Summary |
static String |
VERSION
the version of the activiti library |
VERSION
static final String VERSION
- the version of the activiti library
- See Also:
- Constant Field Values
getName
String getName()
- The name as specified in 'process-engine-name' in
the camunda.cfg.xml configuration file.
The default name for a process engine is 'default
getRepositoryService
RepositoryService getRepositoryService()
getRuntimeService
RuntimeService getRuntimeService()
getFormService
FormService getFormService()
getTaskService
TaskService getTaskService()
getHistoryService
HistoryService getHistoryService()
getIdentityService
IdentityService getIdentityService()
getManagementService
ManagementService getManagementService()
getAuthorizationService
AuthorizationService getAuthorizationService()
close
void close()
Copyright © 2014 camunda services GmbH. All Rights Reserved.