[
https://issues.apache.org/jira/browse/CAMEL-25517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18125783#comment-18125783
]
Claus Ibsen commented on CAMEL-25517:
-------------------------------------
The examples come from apache/camel-jbang-examples (camel-jbang-core downloads
them at build time), so the change is made there, one example per PR, and
reaches Camel with the next sync of the examples. Ladder examples first:
connect/http-client, contracts/openapi-client, contracts/openapi-server,
ai/langchain4j-chat, ai/docling-langchain4j-rag.
_Claude Code on behalf of Claus Ibsen_
> camel-jbang - the shipped examples keep their values in variables, not
> exchange properties
> ------------------------------------------------------------------------------------------
>
> Key: CAMEL-25517
> URL: https://issues.apache.org/jira/browse/CAMEL-25517
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 4.23.0
>
>
> Camel favours variables for the values a route keeps for itself. The examples
> shipped with camel-jbang (connect/http-client, contracts/openapi-client,
> contracts/openapi-server) still keep them in exchange properties
> (setProperty, ${exchangeProperty.x}), and AI agents learn from the examples
> through the tools: in the local-model benchmark the model wrote exchange
> properties throughout, and mixed them up with headers (CAMEL-25516).
> Use setVariable and ${variable.x} instead. Variables also suit the HTTP
> examples better: unlike headers they do not travel on the HTTP request, and
> the REST producer fills a {sku} path placeholder from a header or a variable.
> Camel's own exchange properties (CamelTimerCounter, CamelCircuitBreakerState)
> stay as they are.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
