davsclaus opened a new pull request, #26639:
URL: https://github.com/apache/camel/pull/26639
## Description
From the round-2 benchmark (series l3, circuit-breaker, twice):
```
camel.resilience4j.circuitbreaker.supplierCircuitBreaker.slidingWindowSize=4
```
an invented per-id form, passed the properties validation and the run died
at startup with "Cannot find getter method: supplierCircuitBreaker on bean:
class java.lang.String when binding property:
circuitbreaker.supplierCircuitBreaker.failureRateThreshold".
`PropertiesChecks` now reports a key with a nested segment under one of the
main model's option groups (resilience4j, faulttolerance, threadpool,
health...), before the catalog check, with the global form and, for
resilience4j, the per-circuit-breaker form in the route:
```
Line 1: circuitbreaker Unknown option (camel.resilience4j has no nested
settings such as circuitbreaker: its options are global,
camel.resilience4j.slidingWindowSize=..., or per circuit breaker in the route:
circuitBreaker: {resilience4jConfiguration: {slidingWindowSize: ...}})
```
The prefixes whose keys nest by design (`camel.component`, `camel.beans`,
`camel.variable`, `camel.kamelet`, `camel.main`, bracketed keys such as
`camel.threadpool.config[x]`) are left to the checks that own them.
## Tests
`SourceValidatorPropertiesTest.aNestedKeyUnderAnOptionGroupIsReported`: the
resilience4j and a faulttolerance nested key are reported, the global form
between them is not. The ai package of camel-jbang-core green.
🤖 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]
