Claus Ibsen created CAMEL-24856:
-----------------------------------
Summary: camel-jbang - the properties validator accepts
camel.resilience4j.circuitbreaker.<id>.<option>, which fails at startup
Key: CAMEL-24856
URL: https://issues.apache.org/jira/browse/CAMEL-24856
Project: Camel
Issue Type: Improvement
Components: camel-jbang
Reporter: Claus Ibsen
{code}
camel.resilience4j.circuitbreaker.supplierCircuitBreaker.slidingWindowSize=4
camel.resilience4j.circuitbreaker.supplierCircuitBreaker.failureRateThreshold=50
{code}
an invented per-id form, passes camel validate (the properties validation says
nothing) and the run dies at startup with {{Cannot find getter method:
supplierCircuitBreaker on bean: class java.lang.String when binding property:
circuitbreaker.supplierCircuitBreaker.failureRateThreshold}}. Seen twice in
series l3 (circuit-breaker), one round each.
The validator should report a {{camel.resilience4j.}} key with more than one
segment after the prefix: the resilience4j options are global
({{camel.resilience4j.slidingWindowSize=4}}, the list from the catalog's main
model) or set per circuit breaker in the route ({{circuitBreaker:
{resilience4jConfiguration: {slidingWindowSize: 4}}}}). The same shape applies
to the other main option groups (camel.faulttolerance, camel.threadpool...): a
nested segment under a known group is not a property.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)