davsclaus opened a new pull request, #106: URL: https://github.com/apache/camel-jbang-examples/pull/106
[CAMEL-25517](https://issues.apache.org/jira/browse/CAMEL-25517) Camel favours variables for the values a route keeps for itself. `contracts/openapi-server` kept the reservation request in an exchange property while `direct:lookup` replaces the body; it now uses `setVariable` and `${variable.reservation[qty]}` (variables travel with the exchange into the called route, as properties do). One example per PR, as #104 and #105. - `openapi-server.camel.yaml`: `setProperty` → `setVariable`, `${exchangeProperty.reservation[...]}` → `${variable.reservation[...]}` - `metadata.json`: teaches `setVariable`; catalog regenerated with `./generate-catalog.sh` Checked: `camel validate yaml --canonical` reports nothing; `camel test run contracts/openapi-server/test` passes, including the 200 reservation and the 409 for short stock (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]
