davsclaus opened a new pull request, #115:
URL: https://github.com/apache/camel-jbang-examples/pull/115
CAMEL-25755: the connect-service rung has one JMS example, artemis, which
puts orders on a queue and takes them off. This adds traditional messaging
beyond that, in a new example right after it: request-reply, redelivery with a
dead letter queue, and a topic.
## What
- **`connect-service/jms-request-reply`** on an Artemis broker from `camel
infra run artemis`, with the web shop orders:
- `reserve-order` asks a stock service with request-reply
(`exchangePattern: InOut`; `variableReceive: answer` keeps the order as the
body).
- **ORD-1003 cannot be reserved** (not enough `CAMEL-CAP`). The route's
`deadLetterChannel` redelivers it three times, then moves the original order to
`orders.dead`.
- **Reserved orders** go to the topic `orders.reserved`, which `shipping`
and `invoicing` both subscribe to.
- **README** with the usual sections. Its "Build it step by step" starts
from a file route without a broker, so connecting to Artemis is a step of its
own.
- **Citrus YAML test** (`test/jms-request-reply.citrus.it.yaml`), added to
the CI matrix.
- **Group order:** the example is number 3, after artemis. mqtt,
kafka-orders, ftp and camel-1-tribute move down by one. The catalog and the
README tables are regenerated with `generate-catalog.sh`.
## Checks
- `camel validate yaml --canonical` reports nothing.
- The routes run on the released Camel 4.23.0 and log what the README shows.
- The Citrus test passes (TEST SUCCESS). I ran it locally against an Artemis
started by hand. On my machine the Docker disk is 98% full, and the `camel
infra` broker blocks producers above 90%. That is fixed in apache/camel#28056
(CAMEL-25754). The CI runners have the disk space.
_Claude Code on behalf of davsclaus_
🤖 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]
