[jira] [Work started] (CAMEL-25517) camel-jbang - the shipped examples keep their values in variables, not exchange properties

["Claus Ibsen (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-25517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on CAMEL-25517 started by 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)