davsclaus opened a new pull request, #105:
URL: https://github.com/apache/camel-jbang-examples/pull/105

   [CAMEL-25517](https://issues.apache.org/jira/browse/CAMEL-25517)
   
   Camel favours variables for the values a route keeps for itself. 
`contracts/openapi-client` kept the order id and the line's sku in exchange 
properties for the log; it now uses `setVariable` and `${variable.x}`, also in 
the `onException` that logs a 409. The `sku` header that fills the `{sku}` path 
parameter of `reserveStock` stays a header.
   
   One example per PR, as #104 for http-client.
   
   - `openapi-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 
contracts/openapi-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]

Reply via email to