camel_core/
lib.rs

1//! # Camel Core
2//!
3//! This crate provides the core functionality for the Apache Camel implementation in Rust.
4//!
5//! ## Tracer EIP
6//!
7//! The Tracer Enterprise Integration Pattern (EIP) provides automatic message flow tracing
8//! throughout your Camel routes. It captures detailed information about each step as messages
9//! flow through the integration routes, helping with debugging, monitoring, and observability.
10//!
11//! ### Configuration
12//!
13//! You can configure the tracer in your `Camel.toml` file:
14//!
15//! ```toml
16//! [observability.tracer]
17//! enabled = true
18//! detail_level = "minimal"  # minimal | medium | full
19//!
20//! [observability.tracer.outputs.stdout]
21//! enabled = true
22//! format = "json"
23//! ```
24//!
25//! Or enable it programmatically:
26//!
27//! ```ignore
28//! use camel_core::CamelContext;
29//! let mut ctx = CamelContext::builder().build().await.unwrap();
30//! ctx.set_tracing(true).await;
31//! ```
32//!
33//! ### Span Fields
34//!
35//! Each trace span includes the following fields:
36//!
37//! - `correlation_id`: Unique identifier that links all spans in a single message flow
38//! - `route_id`: Identifier for the route being traced
39//! - `step_id`: Unique identifier for this specific step in the route
40//! - `step_index`: Sequential index of this step within the route
41//! - `timestamp`: When the step was executed (Unix timestamp)
42//! - `duration_ms`: How long the step took to execute in milliseconds
43//! - `status`: The status of the step execution (e.g., "success", "error")
44//!
45//! ### Detail Levels
46//!
47//! The tracer supports three levels of detail:
48//!
49//! - **Minimal**: Includes only the base fields listed above
50//! - **Medium**: Includes the base fields plus:
51//!   - `headers_count`: Number of message headers
52//!   - `body_type`: Type of the message body
53//!   - `has_error`: Whether the message contains an error
54//!   - `output_body_type`: Type of the output body after processing
55//! - **Full**: Includes all fields from Minimal and Medium plus:
56//!   - Up to 3 message headers (`header_0`, `header_1`, `header_2`)
57//!
58//! //! Configuration types for the Tracer EIP live in `camel-core` rather than `camel-config`
59//! //! to avoid a circular dependency — `camel-config` depends on `camel-core`.
60//!
61pub mod claim_check;
62pub mod context;
63mod context_builder;
64pub mod datasource;
65pub mod health_registry;
66pub(crate) mod hot_reload;
67pub mod idempotent;
68pub mod language_registry;
69pub mod lifecycle;
70mod registry;
71// Re-export idempotent registry types for use in lifecycle layers (which
72// are forbidden by the hexagonal boundary test from importing
73// `crate::registry::` directly). Use `crate::IdempotentRegistry` etc.
74pub(crate) use registry::{
75    ClaimCheckRegistry, IdempotentRegistry, SharedClaimCheckRegistry, SharedIdempotentRegistry,
76};
77pub(crate) mod shared;
78pub mod startup_validation;
79pub mod step;
80pub mod template;
81
82#[cfg(feature = "internal-adapters")]
83pub mod route {
84    pub use crate::lifecycle::adapters::route_compiler::{
85        RouteChannelService, compose_pipeline, compose_pipeline_with_contracts,
86        compose_pipeline_with_handler, compose_traced_pipeline,
87    };
88    pub use crate::lifecycle::adapters::route_types::Route;
89    pub use crate::lifecycle::adapters::step_compilers::CompiledStep;
90    pub use crate::lifecycle::application::route_definition::*;
91    pub use crate::lifecycle::domain::route::RouteSpec;
92}
93
94#[cfg(feature = "internal-adapters")]
95pub mod route_controller {
96    pub use crate::lifecycle::adapters::route_controller::*;
97}
98
99pub mod supervising_route_controller {
100    pub use crate::lifecycle::adapters::controller_actor::spawn_supervision_task;
101}
102
103pub mod reload_watcher {
104    pub use crate::hot_reload::adapters::reload_watcher::*;
105    pub use crate::hot_reload::application::FunctionReloadContext;
106    pub use crate::hot_reload::application::execute_reload_actions;
107    pub use crate::hot_reload::domain::ReloadAction;
108}
109
110pub use crate::hot_reload::adapters::ReloadWatcher;
111pub use crate::hot_reload::application::FunctionReloadContext;
112pub use crate::hot_reload::application::execute_reload_actions;
113pub use crate::hot_reload::domain::ReloadAction;
114pub use crate::lifecycle::adapters::controller_actor::RouteControllerHandle;
115pub use crate::lifecycle::adapters::controller_actor::spawn_controller_actor;
116pub use crate::lifecycle::adapters::controller_actor::spawn_supervision_task;
117#[cfg(feature = "internal-adapters")]
118pub use crate::lifecycle::adapters::exchange_uow::ExchangeUoWLayer;
119#[cfg(feature = "internal-adapters")]
120pub use crate::lifecycle::adapters::redb_journal::{
121    JournalDurability, JournalEntry, JournalInspectFilter, RedbJournalOptions,
122    RedbRuntimeEventJournal,
123};
124#[cfg(feature = "internal-adapters")]
125pub use crate::lifecycle::adapters::route_controller::DefaultRouteController;
126#[cfg(feature = "internal-adapters")]
127pub use crate::lifecycle::adapters::route_types::Route;
128#[cfg(feature = "internal-adapters")]
129pub use crate::lifecycle::adapters::{
130    InMemoryCommandDedup, InMemoryEventPublisher, InMemoryProjectionStore, InMemoryRouteRepository,
131    InMemoryRuntimeStore, RuntimeExecutionAdapter,
132};
133pub use crate::lifecycle::application::runtime_bus::RuntimeBus;
134pub use crate::lifecycle::application::{BuilderStep, RouteDefinition};
135pub use crate::lifecycle::domain::{
136    LanguageRegistryError, RouteLifecycleCommand, RouteRuntimeAggregate, RouteRuntimeState,
137    RuntimeEvent,
138};
139pub use crate::lifecycle::ports::{
140    CommandDedupPort, EventPublisherPort, InFlightCountResult, ProjectionStorePort,
141    RouteRepositoryPort, RouteStatusProjection, RuntimeEventJournalPort, RuntimeExecutionPort,
142    RuntimeUnitOfWorkPort,
143};
144pub use crate::shared::components::domain::Registry;
145pub use crate::shared::observability::adapters::TracingProcessor;
146pub use crate::shared::observability::domain::{
147    DetailLevel, FileOutput, OutputFormat, StdoutOutput, TracerConfig, TracerOutputs,
148};
149pub use context::CamelContext;
150pub use language_registry::from_config as languages_from_config;
151pub use template::TemplateRegistry;
152
153// Re-export route controller types from camel-api (they live there to avoid cyclic dependencies).
154pub use camel_api::CamelError;
155pub use camel_api::{RouteAction, RouteController, RouteStatus};
156
157impl From<lifecycle::domain::DomainError> for CamelError {
158    fn from(e: lifecycle::domain::DomainError) -> Self {
159        CamelError::RouteError(e.to_string())
160    }
161}
162
163impl From<lifecycle::domain::LanguageRegistryError> for CamelError {
164    fn from(e: lifecycle::domain::LanguageRegistryError) -> Self {
165        CamelError::Config(e.to_string())
166    }
167}
camel_core/lib.rs

camel_core/
lib.rs
