oscerd opened a new pull request, #26018: URL: https://github.com/apache/camel/pull/26018
## Backport of #25992 Cherry-pick of #25992 (CAMEL-24576) onto `camel-4.22.x`. **Original PR:** #25992 — CAMEL-24576: camel-dynamic-router - do not take the subscription predicate from the control message by default **Target branch:** `camel-4.22.x` The cherry-pick applied cleanly. The only file dropped is `docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_23.adoc`, which does not exist on this branch — the upgrade guides for every release line live on `main`. The matching entry for the 4.22 line is added to `camel-4x-upgrade-guide-4_22.adoc` on `main` in a separate doc-sync PR. Everything else ports as-is: this branch already has the `@UriParam(security = ...)` marker support, `SecurityUtils`, and `RecipientList.setAllowedSchemes`. ### What it does `allowPredicateFromMessage` on the `dynamic-router-control` endpoint, default `false`. When it is `false`, a control message that supplies a `predicate` or an `expressionLanguage` is rejected, and the values configured on the endpoint are used instead. `resolveStaticUri` keeps the flag on the optimised URI so `toD` cannot strip it, and the flag is deliberately absent from `URI_PARAMS_TO_HEADER_NAMES` so it can never be set from a message. Subscription parameters now fall back to the endpoint configuration. `allowedSchemes` is added to the `dynamic-router` endpoint and wired into the `RecipientList`, unset by default. The `predicateBean` path and the JMX operations are unchanged. ### Compatibility This changes a default on a maintenance line. A deployment that lets control messages carry their own predicate must set `allowPredicateFromMessage=true`, or switch those subscriptions to `predicateBean`. _Claude Code on behalf of oscerd_ -- 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]
