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 975b5bfef959 docs: upgrade guide notes for the backports to 4.22.3 and
4.18.6 (#29881)
975b5bfef959 is described below
commit 975b5bfef959009449d131f2f8ff9a45fa727063
Author: Claus Ibsen <[email protected]>
AuthorDate: Fri Nov 13 20:49:26 2026 +0100
docs: upgrade guide notes for the backports to 4.22.3 and 4.18.6 (#29881)
The backports merged to camel-4.22.x and camel-4.18.x change behavior, and
their notes were only in the 4.23 guide. Add them to the 4.22.3 and 4.18.6
sections, with the same text:
- CAMEL-24935 camel-pulsar: the producer no longer replaces the body with
the
message id (4.22.3, 4.18.6)
- CAMEL-24937 camel-pqc: FileBasedKeyLifecycleManager restricts keyId to a
flat file name (4.22.3, 4.18.6)
- CAMEL-25104 camel-core: default TLS protocols and cipher suites of
SSLContextParameters (4.22.3, 4.18.6)
- CAMEL-25105 camel-netty: client authentication of sslContextParameters
(4.22.3, 4.18.6)
- CAMEL-24747 camel-core: toD passes the raw URI to useRawUri() components
(4.22.3)
- CAMEL-24903 camel-core: ThrottlingExceptionRoutePolicy opens the circuit
at
once with keepOpen (4.22.3)
Co-Authored-By: Claude Opus 5.5 <[email protected]>
---
.../ROOT/pages/camel-4x-upgrade-guide-4_18.adoc | 42 ++++++++++++++
.../ROOT/pages/camel-4x-upgrade-guide-4_22.adoc | 65 ++++++++++++++++++++++
2 files changed, 107 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 904354370540..c81d2431cf46 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
@@ -806,6 +806,48 @@ The `netty-http` producer no longer sends some of its
endpoint options, such as
query parameters that are not endpoint options are sent, as the documentation
describes. To send a query parameter
that has the same name as an endpoint option, set the query in the
`CamelHttpQuery` header.
+=== camel-pulsar - the producer no longer replaces the body with the message id
+
+After sending, the producer used to overwrite the message body with the
`MessageId` returned by the
+broker, so every step after the `to("pulsar:...")` saw a `MessageId` instead
of the payload, and a route
+such as `.to("pulsar:a").to("pulsar:b")` published a Java-serialized
`MessageId` to the second topic.
+That behaviour dates from the asynchronous send added in 3.20 (CAMEL-16030).
+
+The body is now left untouched, and the assigned id is reported on the new
+`CamelPulsarProducerMessageId` header instead.
+
+A route that read the `MessageId` from the body must read that header instead.
+
+=== camel-pqc - FileBasedKeyLifecycleManager restricts keyId to a flat file
name
+
+`FileBasedKeyLifecycleManager` now confines every key file to its configured
key directory. A `keyId`
+(supplied through the `CamelPQCKeyId` / `CamelPQCNewKeyId` headers) that
contains a forward slash, a
+backslash, a null character, or that would otherwise resolve outside the key
directory is now rejected
+with an `IllegalArgumentException`.
+
+Previously a `keyId` such as `tenant-a/signing` resolved into a subdirectory
of the key directory.
+Deployments that organised keys that way must switch to a flat `keyId` (for
example `tenant-a-signing`).
+Only the file-based manager is affected; the in-memory and cloud-backed
managers were never file-path
+based.
+
+=== camel-core - default TLS protocols and cipher suites of
SSLContextParameters
+
+The default secure socket protocols filter of `SSLContextParameters` now also
excludes `TLSv1` and `TLSv1.1` (so
+`TLSv1.2` is the minimum), and the default cipher suites filter also excludes
the `3DES` cipher suites. The default
+filters of an `SSLServerSocket` are now applied over the default (enabled)
protocols and cipher suites of the JVM, as
+they already were for an `SSLSocket` and `SSLEngine`. Previously they were
applied over all the supported protocols
+and cipher suites, which enabled `TLSv1` and `TLSv1.1` on a server socket
(unless disabled in the JVM security
+configuration).
+
+To use an older protocol (not recommended) configure it explicitly using
`secureSocketProtocols`.
+
+=== camel-netty, camel-netty-http - client authentication of
sslContextParameters
+
+A Netty consumer using `sslContextParameters` now uses the client
authentication of its server parameters
+(`clientAuthentication` of `SSLContextServerParameters`, or
`camel.ssl.clientAuthentication` with global SSL), also
+when the `needClientAuth` option is not enabled. Previously
`needClientAuth=false` (the default) turned the client
+authentication off.
+
== 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 96dbceacc041..cd163d4189af 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
@@ -692,6 +692,71 @@ The `netty-http` producer no longer sends some of its
endpoint options, such as
query parameters that are not endpoint options are sent, as the documentation
describes. To send a query parameter
that has the same name as an endpoint option, set the query in the
`CamelHttpQuery` header.
+=== camel-pulsar - the producer no longer replaces the body with the message id
+
+After sending, the producer used to overwrite the message body with the
`MessageId` returned by the
+broker, so every step after the `to("pulsar:...")` saw a `MessageId` instead
of the payload, and a route
+such as `.to("pulsar:a").to("pulsar:b")` published a Java-serialized
`MessageId` to the second topic.
+That behaviour dates from the asynchronous send added in 3.20 (CAMEL-16030).
+
+The body is now left untouched, and the assigned id is reported on the new
+`CamelPulsarProducerMessageId` header instead.
+
+A route that read the `MessageId` from the body must read that header instead.
+
+=== camel-pqc - FileBasedKeyLifecycleManager restricts keyId to a flat file
name
+
+`FileBasedKeyLifecycleManager` now confines every key file to its configured
key directory. A `keyId`
+(supplied through the `CamelPQCKeyId` / `CamelPQCNewKeyId` headers) that
contains a forward slash, a
+backslash, a null character, or that would otherwise resolve outside the key
directory is now rejected
+with an `IllegalArgumentException`.
+
+Previously a `keyId` such as `tenant-a/signing` resolved into a subdirectory
of the key directory.
+Deployments that organised keys that way must switch to a flat `keyId` (for
example `tenant-a-signing`).
+Only the file-based manager is affected; the in-memory and cloud-backed
managers were never file-path
+based.
+
+=== camel-core - default TLS protocols and cipher suites of
SSLContextParameters
+
+The default secure socket protocols filter of `SSLContextParameters` now also
excludes `TLSv1` and `TLSv1.1` (so
+`TLSv1.2` is the minimum), and the default cipher suites filter also excludes
the `3DES` cipher suites. The default
+filters of an `SSLServerSocket` are now applied over the default (enabled)
protocols and cipher suites of the JVM, as
+they already were for an `SSLSocket` and `SSLEngine`. Previously they were
applied over all the supported protocols
+and cipher suites, which enabled `TLSv1` and `TLSv1.1` on a server socket
(unless disabled in the JVM security
+configuration).
+
+To use an older protocol (not recommended) configure it explicitly using
`secureSocketProtocols`.
+
+=== camel-netty, camel-netty-http - client authentication of
sslContextParameters
+
+A Netty consumer using `sslContextParameters` now uses the client
authentication of its server parameters
+(`clientAuthentication` of `SSLContextServerParameters`, or
`camel.ssl.clientAuthentication` with global SSL), also
+when the `needClientAuth` option is not enabled. Previously
`needClientAuth=false` (the default) turned the client
+authentication off.
+
+=== camel-core - toD passes the raw URI to useRawUri() components
+
+Components that override `useRawUri()` to return `true` (such as `kamelet`,
`master`, and `webhook`) now
+receive the original, un-encoded URI when the endpoint is resolved dynamically
via `toD`, exactly as they
+already did via the static `to` DSL.
+
+Before this change, `toD` passed the URL-encoded (normalised) form to such
components, causing parameter
+values containing special characters (`%`, `+`, `?`, `=`, `@`, `|`) to arrive
double-encoded at the
+component.
+
+This is a bug fix (CAMEL-24747). Routes that relied on `toD` passing the
encoded form to a `useRawUri()`
+component will now see the original raw value instead. For all other
components (`useRawUri()` returns
+`false`), behaviour is unchanged.
+
+=== camel-core - ThrottlingExceptionRoutePolicy opens the circuit at once with
keepOpen
+
+`ThrottlingExceptionRoutePolicy.setKeepOpen(true)` now opens the circuit
immediately and synchronously (the consumer
+is suspended before the setter returns) rather than waiting for the next
`onExchangeDone()` callback.
+This is the intended behaviour and makes the `keepOpen` toggle deterministic,
but callers that previously
+relied on the setter being inert until an exchange arrived must be aware of
the change.
+Setting `keepOpen` back to `false` remains deferred: the half-open timer
attempts to close the circuit on
+its next tick (after `halfOpenAfter` milliseconds, default 30 s).
+
== Upgrading from 4.22.1 to 4.22.2
=== camel-lra - only an LRA hosted by the configured coordinator is joined