Uses of Interface
org.apache.camel.StaticService
Packages that use StaticService
Package
Description
Camel Catalog API
Camel Health Check support
Service Provider Interfaces used by the Camel runtime which are plugin strategies.
-
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.interfaceUsed for introspecting beans properties via Java reflection; such as extracting current property values, or updating one or more properties etc.interfaceAVariableRepositorythat can browse the variables.interfaceLocalCliConnectorthat allows Camel CLI to manage local running Camel integrations.interfaceSPI strategy for reloadingCamelContext.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.interfaceManagesExchangeFactory.interfaceStrategy to create thread pools.interfaceAn extendedRoutesBuilderLoaderthat is capable of loading from multiple resources in one unit (such as compiling them together).interfaceA repository which tracks in flightExchanges.interfaceAn assembler to assemble aRequiredModelMBeanwhich can be used to register the object in JMX.interfaceStrategy for management.interfaceA factory to createMessageHistoryinstances.interfaceA resolver that can find classes based on package scanning.interfaceA resolver that can find resources based on package scanning.interfaceComponent for property placeholders and loading properties from sources (such as .properties file from classpath or file system)interfaceSPI strategy for reloading.interfaceSPI strategy for reloadingResourcein an existing runningCamelContextinterfaceSPI for loading resources.interfaceA registry of all REST services running within theCamelContextwhich have been defined and created using the Rest DSL.interfaceController for managing the lifecycle of all theRoute's.interfaceSPI for loadingRoutesBuilderfrom aResource.interfaceA registry which listen for runtime usage ofEndpointduring routing in Camel.interfacePluggable shutdown strategy executed during shutdown of Camel and the active routes.interfaceStrategy for performing checks on startup that can validate whether Camel can be started, or wait for some conditions to be satisfied, before Camel can continue to startup.interfaceTo recordStartupStepduring startup to allow to capture diagnostic information to help troubleshoot Camel applications via various tooling such as Java Flight Recorder.interfaceStrategy for using stream caching.interfaceA supervising capableRouteControllerthat delays the startup of the routes after the camel context startup and takes control of starting the routes in a safe manner.interfaceSPI for tracing messages.interfaceRegistry to cache transformers in memory.interfaceRegistry for type converters.interfaceRegistry to cache validators in memory.interfaceRepository for storing and accessing variables.