Federico Mariani created CAMEL-27061:
----------------------------------------
Summary: camel-spring-boot - properties under the removed
camel.springboot. and camel.component.servlet.mapping. prefixes are ignored
without a log line
Key: CAMEL-27061
URL: https://issues.apache.org/jira/browse/CAMEL-27061
Project: Camel
Issue Type: Bug
Components: camel-spring-boot
Reporter: Federico Mariani
The {{camel.springboot.*}} options were removed in Camel 4.13 (CAMEL-21862),
and the servlet mapping options moved from
{{camel.component.servlet.mapping.*}} to {{camel.servlet.mapping.*}} in Camel
3.10. Spring Boot ignores a property below a bound prefix when there is no
field for it, so an application that still uses an old key starts without error
and the setting has no effect. Nothing is logged.
{code}
camel.springboot.name = myCamel
camel.springboot.main-run-controller = true
camel.springboot.route-controller-supervise-enabled = true
camel.component.servlet.mapping.context-path = /api/*
{code}
The CamelContext keeps its generated name, the run controller does not start,
the supervising route controller stays off, and the Camel servlet stays at
{{/camel/*}}, so the REST calls on {{/api/...}} answer 404.
The camel-test-spring-junit5 and camel-test-spring-junit6 pages still show
{{camel.springboot.name}} in their example.
Expected: a WARN at startup for each such property, naming the property to use
instead ({{camel.main.name}}, {{camel.main.run-controller}},
{{camel.routecontroller.enabled}}, {{camel.servlet.mapping.context-path}}).
{{camel.springboot.lenient-configuration-binding}} is still read and is not
reported.
_Claude Code on behalf of Federico Mariani_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)