Uses of Package
org.camunda.bpm.engine.exception
Packages that use org.camunda.bpm.engine.exception
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 DeploymentsRuntimeService:
For starting and searching ProcessInstancesTaskService:
Exposes operations to manage human (standalone) Tasks,
such as claiming, completing and assigning tasksIdentityService:
Used for managing Users,
Groups 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.
-
Classes in org.camunda.bpm.engine.exception used by org.camunda.bpm.engineClassDescriptionThis exception is thrown, if an operation is not allowed to be executed.
-
Classes in org.camunda.bpm.engine.exception used by org.camunda.bpm.engine.impl
-
Classes in org.camunda.bpm.engine.exception used by org.camunda.bpm.engine.impl.cfg
-
Classes in org.camunda.bpm.engine.exception used by org.camunda.bpm.engine.impl.db
-
Classes in org.camunda.bpm.engine.exception used by org.camunda.bpm.engine.impl.utilClassDescriptionThis exception is thrown, if an entity (case execution, case definition) is not found.