Croway opened a new pull request, #212: URL: https://github.com/apache/camel-spring-boot-examples/pull/212
## Summary - Under Spring Boot 4, Artemis autoconfiguration moved to `spring-boot-starter-artemis`, which the saga poms didn't declare (only raw `artemis-jakarta-client`/`pooled-jms`), so `spring.artemis.*` properties were silently ignored and all 4 services crashed with `connectionFactory must be specified`. Added `spring-boot-starter-artemis`. - `run-local.sh` never redirected output or captured PIDs into the `.pid`/`.log` files that `stop-local.sh` expects, breaking the stop script. Also, `mvn spring-boot:run` always forks a child JVM, so the captured PID was the mvn wrapper, not the actual process — `stop-local.sh` now kills the forked child(ren) too. - Replaced the Red Hat registry AMQ broker image (`registry.redhat.io/amq7/amq-broker-rhel8`, requires authenticated registry credentials) with the unauthenticated `apache/artemis` image, in both the local docker-compose file and the OpenShift resources, since Artemis supports OPENWIRE (and the other protocols the saga services need) out of the box. ## Test plan - [x] `mvn clean package` builds all 4 saga modules with the new dependency - [x] `docker compose -f local-resources/compose.yaml pull` succeeds with no registry auth for both `apache/artemis:latest-alpine` and `quay.io/jbosstm/lra-coordinator:latest` - [x] All 4 services (`payment`, `flight`, `train`, `app`) start cleanly with no `connectionFactory must be specified` crash, JMS routes activate - [x] Full saga execution verified end-to-end via `curl -X POST http://localhost:8084/api/saga?id=1`: train reserved, flight booked, both payments processed over JMS/OPENWIRE - [x] `run-local.sh` correctly writes `.pid`/`.log` files - [x] `stop-local.sh` now actually terminates the JVM processes (not just the mvn wrapper) and stops the containers 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01EbjZemqMg395XFGDRekLBM -- 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]
