Uses of Package
org.apache.camel.spi
Packages that use org.apache.camel.spi
Package
Description
The core Camel API.
Runtime catalog API for validating endpoint URIs, configuration properties, and language expressions.
Cluster API for leader election, namespace-based partitioning, and cluster membership management.
Developer console API for exposing runtime operational information in text and JSON formats.
Health check API for readiness and liveness monitoring of the CamelContext, routes, and components.
Configuration classes for Java Secure Socket Extension (JSSE) SSL/TLS setup.
-
Classes in org.apache.camel.spi used by org.apache.camelClassDescriptionStrategy for intercepting messages sent to endpoints in order to auto-mock them during testing.Pluggable contract for looking up beans by name or type, forming the foundation of Camel's Registry.Marker for a service (or other process) that is only needed while Camel is bootstrapping.Strategy for assigning the name of a
CamelContext.Platform-neutral strategy for loading classes and classpath resources across the different runtimes that Camel supports (standalone JVM, Spring Boot, Quarkus, OSGi, JBang, and others).Pluggable strategy for converting message bodies to and from a serialised byte-stream format, as described in the Data Format documentation.Represents the data type URN which is used for message data type contract.Low-level debugger SPI that firesBreakpointcallbacks asExchanges move through each route node, as described in the Debugger documentation.Registry to cache endpoints in memory.Registry forEndpointServiceLocationto make it easy to find information about usage of external services such as databases, message brokers, cloud systems, that Camel is connecting to.Endpoint strategy with callback invoked when anEndpointis about to be registered to the endpoint registry inCamelContext.A registry which captures exceptions that occurred during message routing and stores them in memory.Factory used byConsumer(andPollingConsumer) to create theExchangethat carries an incoming message into Camel.ManagesExchangeFactory.Strategy to create thread pools.Looks up and instantiates SPI factory classes declared in resource files on the classpath, following theMETA-INF/services/org/apache/camel/service-file convention used throughout Camel.A simple marker interface for an object which holds aCamelContext.A live registry that tracks everyExchangethat is currently being processed within theCamelContext.Pluggable strategy for instantiating objects, optionally performing dependency injection as part of creation.Strategy that wraps theProcessors in a route with interceptors, for cross-cutting concerns such as gathering performance statistics at the processor level.SPI base for every Camel expression and predicate language.Observer SPI that receives callbacks for every significant lifecycle event in aCamelContext.An event listener SPI for logging.SPI that wraps EIPProcessors with instrumentation so that per-exchange statistics can be collected and exposed via JMX MBeans.Assembles aModelMBeanfrom a Camel managed object so it can be registered in theMBeanServer.Top-level SPI for Camel's management and observability layer, coordinating JMX registration, lifecycle events, and statistics collection across all Camel artifacts.Factory for creatingMessageHistoryentries, which together form the audit trail of a singleExchangeas it passes through each node of a route.Strategy for computing the size of message payloads (body and headers) for observation purposes.Meta data for EIPs, components, data formats and other Camel concepts For example to associate labels to Camel componentsAn Uri which has been normalized.SPI for the Camel property-placeholder subsystem, which resolves{{key}}tokens in endpoint URIs, DSL expressions, and configuration values.SPI for plugging a custom reactive (non-blocking) dispatch engine into Camel's internal routing loop.Represents aBeanRepositorywhich may also be capable of binding beans to its repository.Describes a loadable resource such as a file, classpath entry, or HTTP URL.Central configuration bean for the Camel REST DSL, shared byRestConsumerFactory,RestProducerFactory, andRestApiConsumerFactoryimplementations.A live registry of all REST services running within theCamelContextthat were defined using the Camel REST DSL.Central SPI for managing the start, stop, suspend, resume, and reload lifecycle of allRoutes in aCamelContext, as described in the Route Controller documentation.The last error that happened during changing the route lifecycle, i.e. such as when an exception was thrown during starting the route.Per-route lifecycle hook that receives callbacks at each state change and at the beginning and end of everyExchange, enabling dynamic control of route behaviour at runtime.Factory that creates aRoutePolicyinstance for each route automatically at startup, without requiring the policy to be declared per-route in the DSL.Captures the resolved startup order and associated services for aRoute, used byCamelContextandShutdownStrategyto control start and shutdown sequencing.A registry which listen for runtime usage ofEndpointduring routing in Camel.Pluggable strategy that performs the actual graceful shutdown sequence when aCamelContextis stopping.Records namedStartupStepspans duringCamelContextstartup to capture timing and diagnostic information for troubleshooting and performance analysis.Strategy that controls when and how stream-based message bodies (such asInputStream) are buffered so they can be re-read, as described in the Stream Caching documentation.SPI for interceptingExchangeflow at each EIP node in a route for tracing and debugging purposes.Performs message body transformation between twoDataTypes as part of Camel's Transformer contract mechanism.Registry that stores and resolvesTransformerinstances for Camel's data type contract mechanism.Central registry for allTypeConverterinstances available in a Camel type-conversion context.Tracks the lifecycle of a singleExchangeas it flows through the routing engine, and provides hooks forSynchronizationcallbacks and async continuation coordination.Generator to generate UUID strings.Validates message content against a declaredDataType, as described in the Transformer and Validator documentation.Registry that stores and resolvesValidatorinstances for Camel's data type validation mechanism. -
Classes in org.apache.camel.spi used by org.apache.camel.catalog
-
Classes in org.apache.camel.spi used by org.apache.camel.clusterClassDescriptionA simple marker interface for an object which holds a
CamelContext.Marker for an object that exposes a unique id, useful for referencing it in REST, JMX, and tooling APIs.Marker for an object whose id can be injected, such as EIPProcessors created from Camel routes. -
Classes in org.apache.camel.spi used by org.apache.camel.consoleClassDescriptionA simple marker interface for an object which holds a
CamelContext.Marker for an object that exposes a unique id, useful for referencing it in REST, JMX, and tooling APIs.Marker for an object whose id can be injected, such as EIPProcessors created from Camel routes. -
Classes in org.apache.camel.spi used by org.apache.camel.healthClassDescriptionA simple marker interface for an object which holds a
CamelContext.Marker for an object that belongs to a named group, useful for group-related operations such as clustering and JMX APIs.Marker for an object that exposes a unique id, useful for referencing it in REST, JMX, and tooling APIs.Marker for an object whose id can be injected, such as EIPProcessors created from Camel routes. -
Classes in org.apache.camel.spi used by org.apache.camel.spiClassDescriptionPersistent store for in-progress aggregated
Exchangeinstances, used by the Aggregator EIP.Information about the thread and exchange that are inflight.Utilization statistics of this manager.Represents an error event captured by theErrorRegistry.Base interface for backlog event messages that capture exchange snapshots at a point in time, without retaining references to the liveExchange.Passive message capture mechanism that records a rolling window of the last N exchange snapshots as they pass through route nodes, as described in the Backlog Tracer documentation.Snapshot of a single exchange event captured by theBacklogTraceras a message transits a route node.Structure of an introspected class.Structure of an introspected method.Pluggable contract for looking up beans by name or type, forming the foundation of Camel's Registry.State of the breakpoint as either active or suspended.A quick status of the browse queueA source-code-generated, compile-time-optimized bundle ofTypeConverterinstances for use with the type conversion infrastructure.Pluggable injector that participates inCamelBeanPostProcessorbean post-processing to support custom, typically 3rd-party, dependency-injection annotations.Strategy for applying custom configuration to aCamelContextafter it has been created.Decides whichCamelContextinstances aCamelContextTrackeris notified about.Base interface for all Camel events used by theEventNotifierfor notifications aboutExchange,Route,CamelContext, andServicelifecycle changes.Event related toCamelContextlifecycle changes.Event related toExchangeprocessing.Event providing details about how a failure was handled during exchange processing.This interface is implemented by all events that contain an exception and is used to retrieve the exception in a universal way.Event related toRoutelifecycle changes.Event related toServicelifecycle changes.Event related to a Step EIP processing.An advice (before and after) to execute cross-cutting functionality in the Camel routing engine.A configurable SLF4J logger wrapper that carries aLoggingLeveland an optional SLF4JMarker.Platform-neutral strategy for loading classes and classpath resources across the different runtimes that Camel supports (standalone JVM, Spring Boot, Quarkus, OSGi, JBang, and others).SPI that exposes a Camel integration to the Camel CLI for local inspection and control.Strategy for applying custom configuration toComponentinstances as they are created.A fluent builder to create aComponentCustomizerinstance.Used as additional filer mechanism to control if customizers need to be applied or not.A condition to define when a givenExchangematches when is being routed.Pluggable strategy for converting message bodies to and from a serialised byte-stream format, as described in the Data Format documentation.Strategy for applying custom configuration toDataFormatinstances as they are created.A fluent builder to create aDataFormatCustomizerinstance.Used as additional filer mechanism to control if customizers need to be applied or not.Represents the data type URN which is used for message data type contract.Low-level debugger SPI that firesBreakpointcallbacks asExchanges move through each route node, as described in the Debugger documentation.Details about the endpoint serviceEndpoint strategy with callback invoked when anEndpointis about to be registered to the endpoint registry inCamelContext.Various statistics about endpoint utilization, such as from EIP patterns that uses dynamic endpoints.A scoped view over error entries in anErrorRegistry, supporting browsing and clearing.Factory that mints concreteCamelEventinstances for every significant lifecycle and messaging event in the Camel runtime.Observer that receivesCamelEventnotifications fired by the Camel runtime.Factory used byConsumer(andPollingConsumer) to create theExchangethat carries an incoming message into Camel.Listener when a newThreadFactoryis created, which allows to plugin custom behaviour.Looks up and instantiates SPI factory classes declared in resource files on the classpath, following theMETA-INF/services/org/apache/camel/service-file convention used throughout Camel.A simple marker interface for an object which holds aCamelContext.Marker for an object that belongs to a named group, useful for group-related operations such as clustering and JMX APIs.Marker for an object that exposes a unique id, useful for referencing it in REST, JMX, and tooling APIs.Interface to allow pluggable implementation to filter headers to and from Camel message.The direction is either IN or OUT.Marker for an object whose id can be injected, such as EIPProcessors created from Camel routes.A live registry that tracks everyExchangethat is currently being processed within theCamelContext.Information about the inflight exchange.Pluggable strategy for instantiating objects, optionally performing dependency injection as part of creation.AnEndpointwrapper that, when sent to, detours the exchange: before, send to the original endpoint (which can be skipped), then after (optional).InternalProcessorthat Camel routing engine used during routing for cross cutting functionality such as: ExecuteUnitOfWorkKeeping track which route currently is being routed ExecuteRoutePolicyGather JMX performance statics Tracing Debugging Message History Stream CachingTransformer... and more.SPI base for every Camel expression and predicate language.Strategy for applying custom configuration toLanguageinstances as they are created.A fluent builder to create aLanguageCustomizerinstance.Used as additional filer mechanism to control if customizers need to be applied or not.Observer SPI that receives callbacks for every significant lifecycle event in aCamelContext.Low-level JMX bridge that registers and unregisters Camel managed objects in aMBeanServer.Strategy for computing the fullObjectName(domain plus all key-value properties) for every Camel artifact registered in JMX.Strategy that creates the managed wrapper objects Camel registers in JMX for its internal artifacts.Top-level SPI for Camel's management and observability layer, coordinating JMX registration, lifecycle events, and statistics collection across all Camel artifacts.Meta data for EIPs, components, data formats and other Camel concepts For example to associate labels to Camel componentsMime types known to Camel data types and its transformers.Represents a line in a model dumper of the route structure (not with full details such as XML or YAML dump).An Uri which has been normalized.Configuration for OAuth 2.0 Client Credentials grant.Configuration for validating incoming OAuth 2.0 bearer tokens.Result of validating an incoming OAuth 2.0 bearer token.Stable validation failure categories for rejected bearer tokens.Marker interface for event handlers that react toCamelContextlifecycle phases.Exceptionused by anAggregationRepositoryto indicate that an optimistic update error has occurred and that the operation should be retried by the caller.Predicate applied byPackageScanClassResolverduring classpath scanning to determine whether a discovered class should be included in the result set.A strategy capable of applying interceptors to a processor.An entry of detailed information from the recipient uri, which allows thePollDynamicAwareimplementation to prepare the static uri to be used for the optimised poll.Factory for pooled objects or tasks.Utilization statistics of the this factory.Callback for sending a exchange message to a endpoint using anAsyncProcessorcapable producer.Extension point for thePropertiesComponentthat handles property placeholders of the form{{name:remainder}}, wherenamematchesPropertiesFunction.getName().Captures how a singlePropertiesComponentproperty placeholder was resolved, for inspection and tooling.A source of property values for the CamelPropertiesComponentwhen resolving property placeholders.Factory for creating the built-inPropertiesSourceimplementations used by thePropertiesComponent.Extension of the configurer SPI that, in addition to setting properties, can describe the options a target supports.SPI strategy for reloading Camel at runtime when a change is detected.Describes a loadable resource such as a file, classpath entry, or HTTP URL.Listener notified when aResourceis re-loaded at runtime, for example after a route file changes.Validation context to use during validationValidation errorValidation context to use during validationValidation errorCentral configuration bean for the Camel REST DSL, shared byRestConsumerFactory,RestProducerFactory, andRestApiConsumerFactoryimplementations.A live registry of all REST services running within theCamelContextthat were defined using the Camel REST DSL.Details about the REST serviceCentral SPI for managing the start, stop, suspend, resume, and reload lifecycle of allRoutes in aCamelContext, as described in the Route Controller documentation.Marker for an object whose owning route id can be injected.Per-route lifecycle hook that receives callbacks at each state change and at the beginning and end of everyExchange, enabling dynamic control of route behaviour at runtime.SPI that loadsRoutesBuilderinstances from aResourceidentified by file extension.Captures the resolved startup order and associated services for aRoute, used byCamelContextandShutdownStrategyto control start and shutdown sequencing.An edge in the topology representing a connection between two routes via a shared endpoint.An external endpoint representing a remote system that a route communicates with.A node in the topology representing a route.The result of computing route topology.Statistics gathered about the endpoint.An entry of detailed information from the recipient uri, which allows theSendDynamicAwareimplementation to prepare pre- and post- processor and the static uri to be used for the optimised dynamic to.A Shared (thread safe) internalProcessorthat Camel routing engine used during routing for cross cutting functionality such as: ExecuteUnitOfWorkKeeping track which route currently is being routed ExecuteRoutePolicyGather JMX performance statics Tracing Debugging Message History Stream CachingTransformer... and more.Allows aServiceto prepare for shutdown.A custom simple language function This allows to plugin custom functions to the built-in simple language.Pluggable gate evaluated repeatedly beforeCamelContextfinishes starting, allowing startup to be paused until an external prerequisite is satisfied.Rule for determine if stream caching should be spooled to disk or kept in-memory.Used for selecting if the memory limit is committed or maximum heap memory setting.Utilization statistics of stream caching.Extension ofRouteControllerthat adds resilient, backoff-based startup supervision for routes, as described in the Route Controller documentation.An extension toSynchronizationwhich provides route awareness capabilities.Low-level SPI for constructingExecutorServiceandScheduledExecutorServiceinstances from aThreadPoolProfileand aThreadFactory.A named, reusable configuration template forThreadPoolExecutorsettings managed by theExecutorServiceManager.A nested interface representing the configuration options for this tokenizer.Performs message body transformation between twoDataTypes as part of Camel's Transformer contract mechanism.Composite lookup key for theTransformerRegistry, encoding a from-DataType/ to-DataTypepair as a single string value for efficient map-based lookup.Registry that stores and resolvesTransformerinstances for Camel's data type contract mechanism.Central registry for allTypeConverterinstances available in a Camel type-conversion context.Utilization statistics of the registry.Holds a type convertible pair.Tracks the lifecycle of a singleExchangeas it flows through the routing engine, and provides hooks forSynchronizationcallbacks and async continuation coordination.Validates message content against a declaredDataType, as described in the Transformer and Validator documentation.Key used inValidatorRegistryinCamelContext, to ensure a consistent lookup.Repository for storing and accessing variables. -
Classes in org.apache.camel.spi used by org.apache.camel.support.jsse