org.mule.runtime.core.api.component

Interface Component

All Superinterfaces:

FlowConstructAware, Function<org.reactivestreams.Publisher<Event>,org.reactivestreams.Publisher<Event>>, Processor, ReactiveProcessor

All Known Subinterfaces:

JavaComponent

All Known Implementing Classes:

AbstractComponent, AbstractJavaComponent, DefaultJavaComponent, PooledJavaComponent, SimpleCallableJavaComponent

public interface Component
extends Processor, FlowConstructAware

A Component component processes a Event by invoking the component instance that has been configured, optionally returning a result.

Implementations of Component can use different types of component implementation, implement component instance pooling or implement bindings which allow for service composition.

Nested Class Summary

Nested classes/interfaces inherited from interface org.mule.runtime.core.api.processor.ReactiveProcessor

ReactiveProcessor.ProcessingType

Method Summary

Modifier and Type	Method and Description
default ReactiveProcessor.ProcessingType	getProcessingType() In order for Mule to determine the best way to execute different processors based on the chosen ProcessingStrategy it needs to know the type of work the message processor will be performing and if it is ReactiveProcessor.ProcessingType.BLOCKING, ReactiveProcessor.ProcessingType.CPU_INTENSIVE intensive or neither (ReactiveProcessor.ProcessingType.CPU_LITE).
ComponentStatistics	getStatistics() Component statistics are used to gather component statistics such as sync/async invocation counts and total and average execution time.

Methods inherited from interface org.mule.runtime.core.api.processor.Processor

apply, process

Methods inherited from interface java.util.function.Function

andThen, compose, identity

Methods inherited from interface org.mule.runtime.core.api.construct.FlowConstructAware

setFlowConstruct

Method Detail

getStatistics

ComponentStatistics getStatistics()

Component statistics are used to gather component statistics such as sync/async invocation counts and total and average execution time.

getProcessingType

default ReactiveProcessor.ProcessingType getProcessingType()

Description copied from interface: ReactiveProcessor

In order for Mule to determine the best way to execute different processors based on the chosen ProcessingStrategy it needs to know the type of work the message processor will be performing and if it is ReactiveProcessor.ProcessingType.BLOCKING, ReactiveProcessor.ProcessingType.CPU_INTENSIVE intensive or neither (ReactiveProcessor.ProcessingType.CPU_LITE).

Specified by:

getProcessingType in interface ReactiveProcessor

Returns:

the processing type for this processor.