You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by da...@apache.org on 2026/09/11 05:28:02 UTC

(camel) 01/01: CAMEL-24676: Sync the camel-jgroups 4.22.1 upgrade guide entry to main

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

davsclaus pushed a commit to branch doc-sync/CAMEL-24676-4_22-upgrade-guide
in repository https://gitbox.apache.org/repos/asf/camel.git

commit 0c10c1620f3a9b62162e2050f1e785fcaaf916a6
Author: Claus Ibsen <cl...@gmail.com>
AuthorDate: Fri Sep 11 07:27:46 2026 +0200

    CAMEL-24676: Sync the camel-jgroups 4.22.1 upgrade guide entry to main
    
    The camel-jgroups deserialization filter was backported to camel-4.22.x in #26281,
    which added an upgrade guide entry for that release line to
    camel-4x-upgrade-guide-4_22.adoc on the maintenance branch.
    
    The camel-4x-upgrade-guide-4_XX.adoc files on main are the canonical history across
    all releases, so the same entry is added here. Without it main's 4.22 upgrade guide
    drifts out of sync with what actually ships on camel-4.22.x.
    
    Doc-only, verbatim copy of the entry on the maintenance branch.
    
    Co-Authored-By: Claude Opus 5 (1M context) <no...@anthropic.com>
    Signed-off-by: Claus Ibsen <cl...@gmail.com>
---
 .../ROOT/pages/camel-4x-upgrade-guide-4_22.adoc    | 26 ++++++++++++++++++++++
 1 file changed, 26 insertions(+)

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 b7d7948545c2..177394351bbe 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
@@ -1937,3 +1937,29 @@ When `clientRequestValidation` is enabled and the REST service declares a requir
 message body is no longer replaced with a `String` version of itself. That conversion corrupted binary
 payloads such as `application/octet-stream`. The body is still read to check that it is present, using
 stream caching so it stays re-readable, but it now keeps its original type.
+
+=== camel-jgroups - the consumer applies a deserialization filter by default
+
+The consumer maps an incoming cluster message to the exchange body by calling
+`org.jgroups.Message.getObject()`, which Java-deserializes the payload. The class of that body is
+now checked against a JEP-290 `java.io.ObjectInputFilter`, resolved through
+`DeserializationFilterHelper`. Previously no filter was applied at all, and any type a cluster peer
+sent was routed.
+
+When no explicit pattern is configured, the JVM-wide `jdk.serialFilter` is honoured if set,
+otherwise the shared Camel default allow-list is applied (it permits standard Java and Apache Camel
+types and denies `java.net.**`). Routes that exchange their own classes over the cluster must widen
+it through the new `deserializationFilter` endpoint option, for example:
+
+[source,java]
+----
+from("jgroups:clusterName?deserializationFilter=com.example.model.**;java.**;!*")
+----
+
+Setting `deserializationFilter=*` accepts any type and so restores the previous behavior. A refused
+message is not routed; it is reported to the consumer's `ExceptionHandler`, which logs it at WARN
+level by default.
+
+Note that JGroups deserializes the payload inside its own receive path, so this check is a
+defense-in-depth allow-list on the resulting body type. The JVM-wide `jdk.serialFilter`, together
+with a channel secured with `AUTH` and encryption, remain the primary mitigations.