Uses of Interface
org.camunda.bpm.engine.ResourceReport

Packages that use ResourceReport

Package	Description
org.camunda.bpm.engine	Public API of the Camunda Platform engine. 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 Deployments RuntimeService: For starting and searching ProcessInstances TaskService: Exposes operations to manage human (standalone) Tasks, such as claiming, completing and assigning tasks IdentityService: Used for managing Users, Groups and the relations between them ManagementService: Exposes engine admin and maintenance operations, which have no relation to the runtime execution of business processes HistoryService: Exposes information about ongoing and past process instances. FormService: Access to form data and rendered forms for starting new process instances and completing tasks.
org.camunda.bpm.engine.impl.bpmn.parser

Uses of ResourceReport in org.camunda.bpm.engine

Fields in org.camunda.bpm.engine with type parameters of type ResourceReport

Modifier and Type	Field	Description
protected List<ResourceReport>	ParseException.resorceReports

Methods in org.camunda.bpm.engine that return types with arguments of type ResourceReport

Modifier and Type	Method	Description
List<ResourceReport>	ParseException.getResorceReports()

Uses of ResourceReport in org.camunda.bpm.engine.impl.bpmn.parser

Classes in org.camunda.bpm.engine.impl.bpmn.parser that implement ResourceReport

Modifier and Type	Class	Description
class	ResourceReportImpl	Resource report created during resource parsing