Uses of Interface
io.camunda.zeebe.engine.processing.deployment.model.element.ExecutableCatchEventSupplier
Packages that use ExecutableCatchEventSupplier
Package
Description
-
Uses of ExecutableCatchEventSupplier in io.camunda.zeebe.engine.processing.bpmn.behavior
Methods in io.camunda.zeebe.engine.processing.bpmn.behavior with type parameters of type ExecutableCatchEventSupplierModifier and TypeMethodDescription<T extends ExecutableCatchEventSupplier>
Either<Failure, Void> BpmnEventSubscriptionBehavior.subscribeToEvents(T element, BpmnElementContext context) -
Uses of ExecutableCatchEventSupplier in io.camunda.zeebe.engine.processing.common
Methods in io.camunda.zeebe.engine.processing.common with parameters of type ExecutableCatchEventSupplierModifier and TypeMethodDescriptionCatchEventBehavior.subscribeToEvents(BpmnElementContext context, ExecutableCatchEventSupplier supplier) -
Uses of ExecutableCatchEventSupplier in io.camunda.zeebe.engine.processing.deployment.model.element
Classes in io.camunda.zeebe.engine.processing.deployment.model.element that implement ExecutableCatchEventSupplierModifier and TypeClassDescriptionclassclassfinal classclassclassclassclassExecutableFlowElementContainer is currently used to represent processes as well (Process), which may seem counter intuitive; at the moment, the reason is that sub processes are also modelled using the same class, and sub processes need to reuse the logic for both.classclassclassExecutable* prefix in order to avoid confusion with model API classes.classfinal classclassfinal class