davsclaus opened a new pull request, #83: URL: https://github.com/apache/camel-jbang-examples/pull/83
Rung 6 of the ladder from CAMEL-24808: connecting to one external service, started by the Camel CLI with `camel infra run`. No compose files any more; the READMEs say `camel infra run <service>` in one terminal and `camel run *` in the other, and the Citrus tests start the service themselves with the `camel: infra: run:` action, so nothing must be running beforehand. Six examples under `connect-service/`: - `sql` (rewritten): a customers table in Postgres; the three orders register their customers with an insert whose `ON CONFLICT` counts orders, and a report lists the table every ten seconds. - `mqtt` (rewritten): cold-room temperature sensors publish JSON on a Mosquitto topic; the consumer logs each reading and warns above 8 degrees. The test publishes a warm reading itself. - `kafka-orders` (route-topology rewritten around the shop): shared validation route with `stop` for the pending order, `CamelKafkaKey` per order, dispatch multicasting to fulfilment and notifications; the README points at `camel cmd route-topology`. - `artemis` (rewritten): the orders queue on Artemis, intake and processing routes. - `ftp` (rewritten): an order on the shipments queue becomes a file on the courier's FTP server, both services started with one `camel infra run artemis ftp`. - `camel-1-tribute` (moved from beginner): the timer counter was empty because it read an exchange property, now `includeMetadata` and the header; output goes to `outbox/` since `test/` holds the Citrus test. All six tests pass locally. Catalog regenerated, CI matrix entries replace the old FTP and MQTT ones. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01Bp3538HRBPMQkb5ta9xRaj -- 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]
