Uses of Package
org.camunda.bpm.engine.impl.interceptor
Package
Description
Public API of the Camunda Platform engine.
Typical usage of the API starts by the creation of a
Through the services obtained from such a
Typical usage of the API starts by the creation of a
ProcessEngineConfiguration
(typically based on a configuration file), from which a ProcessEngine
can be obtained.Through the services obtained from such a
ProcessEngine
, BPM and workflow operation
can be executed:RepositoryService
:
Manages Deployment
sRuntimeService
:
For starting and searching ProcessInstance
sTaskService
:
Exposes operations to manage human (standalone) Task
s,
such as claiming, completing and assigning tasksIdentityService
:
Used for managing User
s,
Group
s and the relations between themManagementService
:
Exposes engine admin and maintenance operations,
which have no relation to the runtime execution of business processesHistoryService
:
Exposes information about ongoing and past process instances.FormService
:
Access to form data and rendered forms for starting new process instances and completing tasks.API implementation classes, which shouldn't directly be used by end-users.
-
-
-
-
-
-
-
ClassDescriptionThe command executor for internal usage/
-
-
-
-
-
-
-
-
-
-
-
ClassDescriptionThe command executor for internal usage/Interceptor responsible for handling calls to 'user code'.A command interceptor to catch
ProcessEngineException
errors and assign error codes. -
-
-
-
-
-
-
-
-
-
ClassDescriptionThe command executor for internal usage/
-
ClassDescriptionThe command executor for internal usage/
-
ClassDescriptionIn contrast to
CommandContext
, this context holds resources that are only valid during execution of a single command (i.e. -
-
-
-
-
-
-
-
-
ClassDescriptionThe command executor for internal usage/
-
-
-
-
-
-
-
-
ClassDescriptionThe command executor for internal usage/
-
ClassDescriptionBase interceptor class for handling transactions for a command.An invocation of an atomic operationCommand context lifecycle eventsThe command executor for internal usage/In contrast to
CommandContext
, this context holds resources that are only valid during execution of a single command (i.e.Holds the contextual process data.
New context properties are always part of a section that can be started byProcessDataContext.pushSection(ExecutionEntity)
. -
ClassDescriptionAn invocation of an atomic operationCommand context lifecycle eventsThe command executor for internal usage/
-
-
-
-
-
-
-
-
-
-
-
ClassDescriptionAn invocation of an atomic operationCommand context lifecycle eventsThe command executor for internal usage/
-
-
-
-
-
ClassDescriptionThe command executor for internal usage/
-
ClassDescriptionThe command executor for internal usage/
-
-
-
-