[
https://issues.apache.org/jira/browse/CAMEL-24857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-24857.
---------------------------------
Fix Version/s: 4.23.0
Resolution: Fixed
> camel-jbang - the validator reports a ${...} placeholder used as an endpoint
> option or bean property value: the syntax is {{key}}
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-24857
> URL: https://issues.apache.org/jira/browse/CAMEL-24857
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Reporter: Claus Ibsen
> Priority: Major
> Fix For: 4.23.0
>
>
> Found by the stepwise half of the round-2 local-model benchmark (ten
> camel-jbang-examples built step by step through the camel-jbang-mcp server,
> five runs each, 2026-09-21).
> The model (and people coming from Simple) writes
> {code:yaml}
> period: "${welcome.period}"
> period: ${properties:welcome.period}
> {code}
> or in beans.yaml {{start: ${order.first-number}}}, where Camel's property
> placeholder in an endpoint option or a bean property is
> {{{{welcome.period}}}}. {{camel validate source}} accepts it (verified:
> Validation success), the route reload or the restart then fails with a
> binding error ("Error binding property
> (period=${properties:welcome.period})"), and the writer gets no signal at
> write time. Seven of eight failures of two steps in the series were this.
> The endpoint checks and the bean/properties checks should report a {{${...}}}
> value in an endpoint option (a {{parameters:}} entry or a uri query) or a
> bean property with "a property placeholder is written {{{{key}}}}; ${...} is
> a Simple expression, which is not evaluated here". The runtime binding error
> could say the same when the value starts with ${.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
