This is an automated email from the ASF dual-hosted git repository. davsclaus pushed a commit to branch docs/CAMEL-25964-26068-upgrade-guide-sync in repository https://gitbox.apache.org/repos/asf/camel.git
commit d2d5b5f284b8f379a18e11745817a9989b391075 Author: Claus Ibsen <[email protected]> AuthorDate: Sat Oct 24 15:59:49 2026 +0200 CAMEL-25964, CAMEL-26068: upgrade guide - the vertx and netty-http notes for 4.22.3 and 4.18.6 The backports to camel-4.22.x (#28345, #28366) and camel-4.18.x (#28346) are merged, so the 4.22 and 4.18 guides on main get their notes under "Upgrading from 4.22.2 to 4.22.3" and "Upgrading from 4.18.5 to 4.18.6". Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]> Signed-off-by: Claus Ibsen <[email protected]> --- .../modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc | 7 +++++++ .../modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc | 11 +++++++++++ 2 files changed, 18 insertions(+) diff --git a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc index 8491caa57913..80435035efe8 100644 --- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc +++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc @@ -436,6 +436,13 @@ earlier in the route. Signatures created by earlier versions may not verify and need to be created again. +=== camel-vertx - standalone TrustManager on SSLContextParameters is applied + +When configuring TLS through `SSLContextParameters` with a standalone `TrustManager` instance (via `TrustManagersParameters.setTrustManager(...)`), Vert.x components now wrap and apply the configured `TrustManager`. Previously, only `TrustAllTrustManager.INSTANCE` and KeyStore-backed configurations were applied, and other standalone `TrustManager` instances were not set on the underlying Vert.x options. + +When both a `TrustManager` and a keystore are configured on `TrustManagersParameters`, the `TrustManager` is now used, +as with the other components that use `SSLContextParameters`; before, the keystore-based trust options were used. + == Upgrading from 4.18.4 to 4.18.5 === camel-azure-eventhubs diff --git a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc index 8b4172b4e043..5cffe2c01681 100644 --- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc +++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc @@ -236,6 +236,17 @@ earlier in the route. Signatures created by earlier versions over a `File`, `Path`, `GenericFile` or other non-`byte[]`/`InputStream` body may not verify and need to be created again. +=== camel-netty-http - securityConfiguration is copied per endpoint + +When `securityConfiguration` is set on the `NettyHttpComponent`, each endpoint now receives an independent copy of the configuration. Modifying `securityConfiguration.*` options on an endpoint URI no longer alters the component-level configuration or other endpoints. + +=== camel-vertx - standalone TrustManager on SSLContextParameters is applied + +When configuring TLS through `SSLContextParameters` with a standalone `TrustManager` instance (via `TrustManagersParameters.setTrustManager(...)`), Vert.x components now wrap and apply the configured `TrustManager`. Previously, only `TrustAllTrustManager.INSTANCE` and KeyStore-backed configurations were applied, and other standalone `TrustManager` instances were not set on the underlying Vert.x options. + +When both a `TrustManager` and a keystore are configured on `TrustManagersParameters`, the `TrustManager` is now used, +as with the other components that use `SSLContextParameters`; before, the keystore-based trust options were used. + == Upgrading from 4.22.1 to 4.22.2 === camel-lra - only an LRA hosted by the configured coordinator is joined
