Croway opened a new pull request, #195: URL: https://github.com/apache/camel-spring-boot-examples/pull/195
## Summary - The `fhir-auth-tx` route only caught `ProtocolException`, but connection failures to the FHIR server actually surface as `FhirClientConnectionException`/`RuntimeCamelException`. Since those went uncaught, the file consumer never marked the input file as handled, causing it to be reprocessed on every poll indefinitely. - Broadened the `onException` clause to cover the actual exceptions thrown, added a bounded redelivery policy with backoff, added a catch-all handler as a backstop, and set `moveFailed` on the file consumer as defense in depth. - The README described a stale `hl7v2.patient`/HL7v2 flow instead of the actual `patients.csv` + transaction Bundle flow, and pointed at a personal GitHub fork (`rkorytkowski/hapi-fhir`) for an auth-enabled HAPI server. Replaced it with a Docker Compose setup (HAPI FHIR JPA server behind an nginx reverse proxy enforcing HTTP Basic auth) under `fhir-auth-tx/containers`, and updated `serverUrl` accordingly. ## Test plan - [x] `mvn verify` passes for the module (existing mocked `MyCamelApplicationTest` still green) - [x] Started the new `docker-compose.yml` (HAPI FHIR + nginx basic-auth proxy) and confirmed `401` without/with wrong credentials, `200` with correct ones - [x] Ran the packaged app against the Docker FHIR server: dropped `patients.csv`, confirmed the transaction Bundle was created successfully - [x] Stopped the FHIR server and dropped another file: confirmed the route retried with backoff, logged the error once, and moved the file to `.camel/` instead of looping forever 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_016WKaCqZQd9uUiQR6QMZJkJ -- 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]
