This is an automated email from the ASF dual-hosted git repository.

davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git


The following commit(s) were added to refs/heads/main by this push:
     new b5caa8cabf7f CAMEL-25964, CAMEL-26068: upgrade guide - the vertx and 
netty-http notes for 4.22.3 and 4.18.6 (#28415)
b5caa8cabf7f is described below

commit b5caa8cabf7fcd7a44bc06c37ae74afb369efa71
Author: Claus Ibsen <[email protected]>
AuthorDate: Sun Oct 25 12:44:12 2026 +0100

    CAMEL-25964, CAMEL-26068: upgrade guide - the vertx and netty-http notes 
for 4.22.3 and 4.18.6 (#28415)
    
    Add the upgrade-guide notes on main for the merged backports: 
camel-netty-http securityConfiguration copied per endpoint (CAMEL-26068) and 
camel-vertx standalone TrustManager on SSLContextParameters (CAMEL-25964) for 
4.22.3, and the camel-vertx note for 4.18.6. The text matches the 4.24 guide.
    
    Co-Authored-By: Claude Opus 5.5 (1M context) <[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 883d3337d835..f48637f725ff 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
@@ -465,6 +465,13 @@ the arguments of the call, as in `Error invoking 
resourceById with [password, re
 username]: ...`, and no longer shows their values. The arguments hold the 
options of the endpoint, such as a password or
 a token, and the message data. The debug log of the call masks the values of 
the sensitive options.
 
+=== 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 d407a14605b2..202add6288a9 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
@@ -265,6 +265,17 @@ the arguments of the call, as in `Error invoking 
resourceById with [password, re
 username]: ...`, and no longer shows their values. The arguments hold the 
options of the endpoint, such as a password or
 a token, and the message data. The debug log of the call masks the values of 
the sensitive options.
 
+=== 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

Reply via email to