Interface StaticService

All Superinterfaces:
AutoCloseable, Service
All Known Subinterfaces:
AsyncProcessorAwaitManager, BeanIntrospection, BrowsableVariableRepository, CliConnector, ContextReloadStrategy, DevConsoleRegistry, DevConsoleResolver, DumpRoutesStrategy, EndpointRegistry, EndpointServiceRegistry, ErrorRegistry, ExchangeFactoryManager, ExecutorServiceManager, ExtendedRoutesBuilderLoader, HealthCheckRegistry, InflightRepository, ManagementMBeanAssembler, ManagementStrategy, MessageHistoryFactory, MessageSizeStrategy, PackageScanClassResolver, PackageScanResourceResolver, PropertiesComponent, ReloadStrategy, ResourceReloadStrategy, ResourceResolver, RestRegistry, RouteController, RoutesBuilderLoader, RuntimeCamelCatalog, RuntimeEndpointRegistry, ShutdownStrategy, SimpleFunctionRegistry, StartupConditionStrategy, StartupStepRecorder, StreamCachingStrategy, SupervisingRouteController, Tracer, TransformerRegistry, TypeConverterRegistry, ValidatorRegistry, VariableRepository
public interface StaticService extends Service
Marker interface indicating that a Service is a "static" service: a singleton within a CamelContext that is created once at context startup and shared for the context lifetime.

Static services are managed differently from ordinary services: the context starts and stops them as part of its own lifecycle rather than per-route or per-endpoint lifecycle. Examples include PropertiesComponent, RestRegistry, InflightRepository, and other context-wide infrastructure services. A service that implements this marker will not be started or stopped multiple times even if multiple routes reference it — the context guarantees exactly one start and one stop across its full lifecycle.

See Lifecycle in the Camel user manual.

See Also: