davsclaus opened a new pull request, #104: URL: https://github.com/apache/camel-jbang-examples/pull/104
[CAMEL-25517](https://issues.apache.org/jira/browse/CAMEL-25517) Camel favours variables for the values a route keeps for itself. `connect/http-client` kept the order id, the line's sku and the quantity in exchange properties; it now uses `setVariable` and `${variable.x}`. Like exchange properties, variables stay in the route (headers would travel on the HTTP request and collide with the `{sku}` path parameter on the server side), and they are copied to each line of the split the same way. AI agents learn Camel from these examples through the camel-jbang-mcp tools: in the local-model benchmark the model wrote exchange properties throughout, as the examples do, and mixed them up with headers (CAMEL-25516). One example per PR; openapi-client, openapi-server and the ai examples follow. - `http-client.camel.yaml`: `setProperty` → `setVariable`, `${exchangeProperty.x}` → `${variable.x}` - `README.md`: *How it works* and the step-by-step prompt say variables - `metadata.json`: teaches `setVariable`; catalog regenerated with `./generate-catalog.sh` Checked: `camel validate yaml --canonical` reports nothing; `camel test run connect/http-client/test` passes (Camel 4.23.0-SNAPSHOT). _Claude Code on behalf of Claus Ibsen_ 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01STT6whBgK1AqsSsUKrnE8m -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
