Uses of Interface
org.apache.camel.StaticService
Packages that use StaticService
Package
Description
Runtime catalog API for validating endpoint URIs, configuration properties, and language expressions.
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.
-
Uses of StaticService in org.apache.camel.catalog
Subinterfaces of StaticService in org.apache.camel.catalogModifier and TypeInterfaceDescriptioninterfaceRuntime catalog which limited API needed by components that supportsComponentVerifierExtension. -
Uses of StaticService in org.apache.camel.console
Subinterfaces of StaticService in org.apache.camel.consoleModifier and TypeInterfaceDescriptioninterfaceA registry for dev console.interfaceA pluggable strategy for resolving dev consoles in a loosely coupled manner -
Uses of StaticService in org.apache.camel.health
Subinterfaces of StaticService in org.apache.camel.health -
Uses of StaticService in org.apache.camel.spi
Subinterfaces of StaticService in org.apache.camel.spiModifier and TypeInterfaceDescriptioninterfaceA manager to handle async routing engine, whenExchanges are being handed over from one thread to another, while the callee thread is blocked waiting for the other threads to complete, before it can continue.interfaceLow-level SPI for reading and writing bean properties via Java reflection, used internally by Camel's property binding infrastructure.interfaceAVariableRepositorythat can browse the variables.interfaceSPI that exposes a Camel integration to the Camel CLI for local inspection and control.interfaceSPI strategy for reloading a runningCamelContextin place.interfaceStrategy for dumping routes during startup dump all loaded routes (incl rests and route templates).interfaceRegistry to cache endpoints in memory.interfaceRegistry forEndpointServiceLocationto make it easy to find information about usage of external services such as databases, message brokers, cloud systems, that Camel is connecting to.interfaceA registry which captures exceptions that occurred during message routing and stores them in memory.interfaceManagesExchangeFactory.interfaceStrategy to create thread pools.interfaceAn extendedRoutesBuilderLoaderthat is capable of loading from multiple resources in one unit (such as compiling them together).interfaceA live registry that tracks everyExchangethat is currently being processed within theCamelContext.interfaceAssembles aModelMBeanfrom a Camel managed object so it can be registered in theMBeanServer.interfaceTop-level SPI for Camel's management and observability layer, coordinating JMX registration, lifecycle events, and statistics collection across all Camel artifacts.interfaceFactory for creatingMessageHistoryentries, which together form the audit trail of a singleExchangeas it passes through each node of a route.interfaceStrategy for computing the size of message payloads (body and headers) for observation purposes.interfaceClasspath scanning strategy for discovering classes by annotation, supertype, or custom predicate across one or more packages, used by Camel at startup to auto-detect components, type converters, and other pluggable types.interfaceA resolver that can find resources based on package scanning.interfaceSPI for the Camel property-placeholder subsystem, which resolves{{key}}tokens in endpoint URIs, DSL expressions, and configuration values.interfaceSPI strategy for reloading Camel at runtime when a change is detected.interfaceSPI strategy for reloadingResources in an already runningCamelContext.interfaceSPI for resolving aResourcefor a specific URI scheme.interfaceA live registry of all REST services running within theCamelContextthat were defined using the Camel REST DSL.interfaceCentral SPI for managing the start, stop, suspend, resume, and reload lifecycle of allRoutes in aCamelContext, as described in the Route Controller documentation.interfaceSPI that loadsRoutesBuilderinstances from aResourceidentified by file extension.interfaceA registry which listen for runtime usage ofEndpointduring routing in Camel.interfacePluggable strategy that performs the actual graceful shutdown sequence when aCamelContextis stopping.interfaceRegistry for custom simple functions.interfaceStrategy that runsStartupConditionchecks during startup to decide whether Camel may start, optionally waiting until the conditions are satisfied.interfaceRecords namedStartupStepspans duringCamelContextstartup to capture timing and diagnostic information for troubleshooting and performance analysis.interfaceStrategy 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.interfaceExtension ofRouteControllerthat adds resilient, backoff-based startup supervision for routes, as described in the Route Controller documentation.interfaceSPI for interceptingExchangeflow at each EIP node in a route for tracing and debugging purposes.interfaceRegistry that stores and resolvesTransformerinstances for Camel's data type contract mechanism.interfaceCentral registry for allTypeConverterinstances available in a Camel type-conversion context.interfaceRegistry that stores and resolvesValidatorinstances for Camel's data type validation mechanism.interfaceRepository for storing and accessing variables.