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 lifecycle;
69mod registry;
70// Re-export idempotent registry types for use in lifecycle layers (which
71// are forbidden by the hexagonal boundary test from importing
72// `crate::registry::` directly). Use `crate::IdempotentRegistry` etc.
73pub(crate) use registry::{
74    ClaimCheckRegistry, IdempotentRegistry, SharedClaimCheckRegistry, SharedIdempotentRegistry,
75};
76pub(crate) mod shared;
77pub mod step;
78pub mod template;
79
80#[cfg(feature = "internal-adapters")]
81pub mod route {
82    pub use crate::lifecycle::adapters::route_compiler::{
83        RouteChannelService, compose_pipeline, compose_pipeline_with_contracts,
84        compose_pipeline_with_handler, compose_traced_pipeline,
85    };
86    pub use crate::lifecycle::adapters::route_types::Route;
87    pub use crate::lifecycle::adapters::step_compilers::CompiledStep;
88    pub use crate::lifecycle::application::route_definition::*;
89    pub use crate::lifecycle::domain::route::RouteSpec;
90}
91
92#[cfg(feature = "internal-adapters")]
93pub mod route_controller {
94    pub use crate::lifecycle::adapters::route_controller::*;
95}
96
97pub mod supervising_route_controller {
98    pub use crate::lifecycle::adapters::controller_actor::spawn_supervision_task;
99}
100
101pub mod reload_watcher {
102    pub use crate::hot_reload::adapters::reload_watcher::*;
103    pub use crate::hot_reload::application::FunctionReloadContext;
104    pub use crate::hot_reload::application::execute_reload_actions;
105    pub use crate::hot_reload::domain::ReloadAction;
106}
107
108pub use crate::hot_reload::adapters::ReloadWatcher;
109pub use crate::hot_reload::application::FunctionReloadContext;
110pub use crate::hot_reload::application::execute_reload_actions;
111pub use crate::hot_reload::domain::ReloadAction;
112pub use crate::lifecycle::adapters::controller_actor::RouteControllerHandle;
113pub use crate::lifecycle::adapters::controller_actor::spawn_controller_actor;
114pub use crate::lifecycle::adapters::controller_actor::spawn_supervision_task;
115#[cfg(feature = "internal-adapters")]
116pub use crate::lifecycle::adapters::exchange_uow::ExchangeUoWLayer;
117#[cfg(feature = "internal-adapters")]
118pub use crate::lifecycle::adapters::redb_journal::{
119    JournalDurability, JournalEntry, JournalInspectFilter, RedbJournalOptions,
120    RedbRuntimeEventJournal,
121};
122#[cfg(feature = "internal-adapters")]
123pub use crate::lifecycle::adapters::route_controller::DefaultRouteController;
124#[cfg(feature = "internal-adapters")]
125pub use crate::lifecycle::adapters::route_types::Route;
126#[cfg(feature = "internal-adapters")]
127pub use crate::lifecycle::adapters::{
128    InMemoryCommandDedup, InMemoryEventPublisher, InMemoryProjectionStore, InMemoryRouteRepository,
129    InMemoryRuntimeStore, RuntimeExecutionAdapter,
130};
131pub use crate::lifecycle::application::runtime_bus::RuntimeBus;
132pub use crate::lifecycle::application::{BuilderStep, RouteDefinition};
133pub use crate::lifecycle::domain::{
134    LanguageRegistryError, RouteLifecycleCommand, RouteRuntimeAggregate, RouteRuntimeState,
135    RuntimeEvent,
136};
137pub use crate::lifecycle::ports::{
138    CommandDedupPort, EventPublisherPort, InFlightCountResult, ProjectionStorePort,
139    RouteRepositoryPort, RouteStatusProjection, RuntimeEventJournalPort, RuntimeExecutionPort,
140    RuntimeUnitOfWorkPort,
141};
142pub use crate::shared::components::domain::Registry;
143pub use crate::shared::observability::adapters::TracingProcessor;
144pub use crate::shared::observability::domain::{
145    DetailLevel, FileOutput, OutputFormat, StdoutOutput, TracerConfig, TracerOutputs,
146};
147pub use context::CamelContext;
148pub use template::TemplateRegistry;
149
150// Re-export route controller types from camel-api (they live there to avoid cyclic dependencies).
151pub use camel_api::CamelError;
152pub use camel_api::{RouteAction, RouteController, RouteStatus};
153
154impl From<lifecycle::domain::DomainError> for CamelError {
155    fn from(e: lifecycle::domain::DomainError) -> Self {
156        CamelError::RouteError(e.to_string())
157    }
158}
159
160impl From<lifecycle::domain::LanguageRegistryError> for CamelError {
161    fn from(e: lifecycle::domain::LanguageRegistryError) -> Self {
162        CamelError::Config(e.to_string())
163    }
164}
camel_core/lib.rs

camel_core/
lib.rs
