Technical articles
Route samples and integration practice
Articles for implementation teams covering route sample capabilities and integration modernization paths in the delivery package.
Core routes and data access
HTTP Listener and Undertow request routingHTTP.Listener, server.port and system.components=undertowhttp gate Undertow; HttpRequestSrv closes the request-response loop, verified with curl.Timer v1.0.1: service-level logging for scheduled routesTimer v1.0.1 adds servicelog per-service logging, structured status fields, and jsonResponseProcessor for stable UTF-8 output.External database routes with externaldbService-level extdb.* datasources, dynamic registry beans, and config-driven target switching for MySQL routes.A route that serves a web pageThe temporary approval form sample: route-served page design, mock boundary, and delete-to-destroy lifecycle.Modernizing legacy integrationEnglish article for integration architects, Camel engineers, automation teams, and robotics workflow implementers.
Data transformation
PlatformHttp v1.0.0: config-driven DS transformConfig-driven DS transform for complex order JSON: conditionaltransform switch, shared functions, stable write-back.PlatformHttp v2.0.0: pluggable DTS via SPI and DataSonnetOne HTTP Listener entry fans a request out to four named transforms via invokeDtsTransform; providers load from services/TransformDS by Java SPI.PlatformHttp v3.0.0: JSONPath order transformExtract orderId with JSONPath at the HTTP entry and write back stable UTF-8 JSON responses.
AI integration
AiAgentDemoSrv: an LLM order assistant built from Camel routeslangchain4j-agent discovers three XML-only order tools by tag — one HTTP entry, multi-turn memory, curl-verified.AI agent integration on a solo budgetOne HTTP entrypoint, a LangChain4j agent, three tagged tools, and a 7-day plan — an API integration loop for under $7.
Robotics
The robot AI approval gateFrom edge inference candidate to one-shot submit: policy validation, HMAC-signed approval, and fail-closed bypass paths.Robot command dispatcher: outbox, receipts, compensation, audit archiveFrom status=accepted to a terminal state — MQTT outbox dispatch, ack/result ingest, state snapshots, compensation marking, and automatic audit archiving.Robot shared safety policyShared robot command safety at the management API: denylist, allowlists, and fail-closed rejection — no command, no outbox.
Industrial protocols
Operations and governance
Route static preflightValidate route configuration without starting the service: generic closure checks, ten scenario profiles, and gate-friendly PASS/FAIL output.Runtime diagnostics: remote troubleshooting that never touches the businessRead-only diagnostics API and CLI: sanitized runtime evidence without touching routes, data, or business traffic.Service runtime transitions: synchronized start/stop and timeout governanceStart/stop APIs wait for the Camel context — shared transitions, idempotent retries, 409 semantics, and a tunable transition timeout.Orchestrating JSON Schema validation routes with the CLIGenerate Draft 2020-12 schemas from message models, then apply the full validation route — with a 400 failure branch.Hardened runtime configuration and CLI boundariesOne platform config file, capabilities off by default, confirmed writes, candidate resource closure, and safe external field aliases.Deployment security with the management APIGuarded service deployment: hardened archive intake, server-owned targets, explicit --yes writes, and backup-based rollback.Action catalog, bounded approval, and operation auditDerive Actions offline, gate eligibility with an exact allowlist, approve a bounded file scope, and query append-only audit events without storing secrets.