mvanhorn opened a new pull request, #8740: URL: https://github.com/apache/camel-quarkus/pull/8740
## Summary Adds integration test coverage confirming the Camel `ErrorRegistry` SPI (CAMEL-23079) can be enabled and configured on Camel Quarkus through `camel.main.*` properties, in JVM and native mode. ## Why this matters #8702 asks for Quarkus configuration support for the new `ErrorRegistry` SPI. As jamesnetherton noted in the issue, the configuration is already handled by `camel-main`, so what's needed is "some test coverage to confirm it works on CQ" - that's what this PR adds, following the existing patterns in `integration-tests/main`. ## What it covers `CoreMainResource` gains a `/test/context/error-registry` endpoint that reports the registry's `enabled`, `maximumEntries`, `timeToLive`, `stackTraceEnabled`, and `size` state from the running `CamelContext`. `application.properties` enables the registry with non-default values (`maximum-entries = 37`, `time-to-live-seconds = 19`) so the test proves the values flow through rather than matching defaults, which also keeps the test immune to the planned TTL-default change mentioned in the issue. `CoreMainTest` asserts the configured values; a second `@QuarkusTest` with a `@TestProfile` overriding `camel.main.error-registry-enabled = false` asserts the disabled path. Both run in native mode via the corresponding `@QuarkusIntegrationTest` subclasses. ## Testing The new assertions run inside the existing `integration-tests/main` module. API usage was verified against `camel-api` 4.20.0 (`CamelContext.getErrorRegistry()`, `ErrorRegistry` accessors, `ErrorRegistryView.size()`). Fixes #8702 -- 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]
