Federico Mariani created CAMEL-27081:
----------------------------------------
Summary: camel-spring-boot - camel.main options that Camel moved,
and unknown camel.main options, are ignored without a log line
Key: CAMEL-27081
URL: https://issues.apache.org/jira/browse/CAMEL-27081
Project: Camel
Issue Type: Bug
Components: camel-spring-boot
Reporter: Federico Mariani
Camel on Spring Boot binds {{camel.main.*}} to a configuration class. Spring
Boot ignores a property below a bound prefix when the class has no field for
it. So a {{camel.main}} option that Camel moved to another group, an option of
Camel Main standalone, or a typo has no effect, and the application starts
without a log line. Camel Main standalone fails the startup for such a property.
{code}
camel.main.backlog-tracing = true
camel.main.route-controller-supervise-enabled = true
camel.main.error-registry-enabled = true
camel.main.debugging = true
camel.main.base-package-scan = com.acme.routes
camel.main.nmae = myCamel
{code}
The backlog tracer, the supervising route controller and the error registry
stay off, the debugger is not enabled, and the CamelContext keeps its generated
name.
The options that Camel moved, from the upgrade guides:
* {{camel.main.xml-routes}}, {{camel.main.xml-rests}},
{{camel.main.xml-route-templates}}: {{camel.main.routes-include-pattern}} (3.8)
* {{camel.main.debugging}}: {{camel.debug.enabled}} (4.2)
* {{camel.main.route-controller-*}}: {{camel.routecontroller.*}} (4.4)
* {{camel.main.backlog-tracing}}, {{camel.main.backlog-tracing-standby}},
{{camel.main.backlog-tracing-templates}}: {{camel.trace.*}} (4.5)
* {{camel.main.error-registry-*}}: {{camel.errorregistry.*}} (4.21)
Expected: a WARN at startup for each {{camel.main}} property that is not an
option, with the option to use instead when Camel moved it.
_Claude Code on behalf of Federico Mariani_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)