Federico Mariani created CAMEL-27073:
----------------------------------------
Summary: camel-main, camel-mdc - camel.mdc.customExchangeHeaders
and camel.mdc.customExchangeProperties fail startup
Key: CAMEL-27073
URL: https://issues.apache.org/jira/browse/CAMEL-27073
Project: Camel
Issue Type: Bug
Components: camel-main
Reporter: Federico Mariani
On Camel Main (and Camel JBang) the {{camel.mdc.*}} options are bound on
{{MDCService}}. The main configuration metadata, main.adoc and the option table
of mdc.adoc list {{camel.mdc.customExchangeHeaders}} and
{{camel.mdc.customExchangeProperties}} (the names Spring Boot and Quarkus use
too), but {{MDCService}} only has {{customHeaders}} and {{customProperties}}.
So the documented options fail startup:
{code}
camel.mdc.enabled=true
camel.mdc.customExchangeHeaders=foo
{code}
{noformat}
PropertyBindingException: Error binding property
(camel.mdc.customExchangeHeaders=foo) with name: customExchangeHeaders on bean:
org.apache.camel.mdc.MDCService@...
{noformat}
With {{camel.main.autoConfigurationFailFast=false}} Camel starts, but the
options do nothing. Only {{camel.mdc.customHeaders}} and
{{camel.mdc.customProperties}} work on Camel Main. The docs mix both names: the
text of mdc.adoc, micrometer-observability.adoc and telemetry-dev.adoc say
{{customHeaders}}, which Spring Boot and Quarkus do not have.
Expected: {{camel.mdc.customExchangeHeaders}} and
{{camel.mdc.customExchangeProperties}} work on Camel Main, as on Spring Boot
and Quarkus. {{customHeaders}} and {{customProperties}} keep working. The docs
use the same names everywhere.
_Claude Code on behalf of Federico Mariani_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)