Croway commented on PR #2078: URL: https://github.com/apache/camel-spring-boot/pull/2078#issuecomment-6736365861
I would hold this backport until we address a compatibility regression in `copyConfigurationProperties`: the new filter discards values assigned programmatically to a starter configuration bean because those assignments are absent from `BoundConfigurationProperties`. I reproduced this using `HttpComponentConfiguration` and `HttpComponent`. Before invoking the customizer: ```java configuration.setSkipRequestHeaders(true); ``` With this external property: ```properties camel.component.http.log-http-activity=true ``` Before this PR, both values reach the component. After this PR, `logHttpActivity` remains `true`, but `skipRequestHeaders` stays `false`: the Java-assigned value is silently filtered out. `lenient-configuration-binding=true` cannot restore it. The fix is valuable: unused catalog defaults should not overwrite values on user-supplied Camel beans, and unset MCP hints should remain unset. However, we should also preserve explicit Java assignments to starter configuration beans before backporting this across all starters. The existing 13 helper tests passed. An added test for this case passes against the pre-PR helper and fails against the PR helper. Validation used PR source temporarily aligned to released Camel 4.22.1 dependencies, rather than the exact 4.22.3-SNAPSHOT dependency set. _Codex on behalf of Federico Mariani_ -- 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]
