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 ed3d719b379c chore: upgrade guide - the pqc note about signing message
bodies over their bytes is part of 4.22.3
ed3d719b379c is described below
commit ed3d719b379c911ae84a387799687c8c739fd47c
Author: Claus Ibsen <[email protected]>
AuthorDate: Fri Oct 23 11:40:07 2026 +0200
chore: upgrade guide - the pqc note about signing message bodies over their
bytes is part of 4.22.3
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
Signed-off-by: Claus Ibsen <[email protected]>
---
.../ROOT/pages/camel-4x-upgrade-guide-4_22.adoc | 30 +++++++++++-----------
1 file changed, 15 insertions(+), 15 deletions(-)
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 dbe1c1b8eb7f..8b4172b4e043 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
@@ -221,6 +221,21 @@ channel of its endpoint, for every operation. To choose a
different channel for
`CamelPubNubOverrideChannel` header (`PubNubConstants.OVERRIDE_CHANNEL`).
Routes that set `CamelPubNubChannel` to pick
the channel of a pubnub producer must set `CamelPubNubOverrideChannel` instead.
+=== camel-pqc - message bodies are signed and verified over their bytes
+
+The `sign`, `verify`, `hybridSign` and `hybridVerify` operations now read a
`java.io.File` or `java.nio.file.Path`
+body, and a file from a file consumer (a `GenericFile` body), as bytes from
the file, the same way as a `byte[]` or
+`InputStream` body. A `String` (or any `CharSequence`) body is encoded as
UTF-8, and any other body that has a binary
+type converter (for example a `java.nio.ByteBuffer`, a
`java.io.ByteArrayOutputStream`, a Netty `ByteBuf` or a Vert.x
+`Buffer`) is signed over those bytes.
+
+A body with no binary representation (for example a `Map` or a POJO) is no
longer signed over its `toString()`: it is
+now rejected with an `InvalidPayloadException`. Convert such a body to a
`String`, `byte[]` or other binary type
+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.
+
== Upgrading from 4.22.1 to 4.22.2
=== camel-lra - only an LRA hosted by the configured coordinator is joined
@@ -2093,21 +2108,6 @@ already UTF-8 (JEP 400), so this is a no-op there; on
Java 17 with a non-UTF-8 d
signature of a non-ASCII `String` payload changes. Binary bodies (`byte[]`,
`InputStream`) are
unaffected, as they are signed byte-for-byte.
-=== camel-pqc - message bodies are signed and verified over their bytes
-
-The `sign`, `verify`, `hybridSign` and `hybridVerify` operations now read a
`java.io.File` or `java.nio.file.Path`
-body, and a file from a file consumer (a `GenericFile` body), as bytes from
the file, the same way as a `byte[]` or
-`InputStream` body. A `String` (or any `CharSequence`) body is encoded as
UTF-8, and any other body that has a binary
-type converter (for example a `java.nio.ByteBuffer`, a
`java.io.ByteArrayOutputStream`, a Netty `ByteBuf` or a Vert.x
-`Buffer`) is signed over those bytes.
-
-A body with no binary representation (for example a `Map` or a POJO) is no
longer signed over its `toString()`: it is
-now rejected with an `InvalidPayloadException`. Convert such a body to a
`String`, `byte[]` or other binary type
-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-sql - Schema-qualified aggregation repository names
The table-name validation in `JdbcAggregationRepository` now accepts
schema-qualified names
