This is an automated email from the ASF dual-hosted git repository.
oscerd pushed a commit to branch camel-4.18.x
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/camel-4.18.x by this push:
new e5f60632d6c0 CAMEL-24421: remove the spring-redis upgrade note from
camel-4.18.x (#25781)
e5f60632d6c0 is described below
commit e5f60632d6c031cb355eb51f146c5c116d675102
Author: Andrea Cosentino <[email protected]>
AuthorDate: Thu Aug 27 06:47:21 2026 +0200
CAMEL-24421: remove the spring-redis upgrade note from camel-4.18.x (#25781)
CAMEL-24421: remove the spring-redis upgrade note from this branch
The camel-4x-upgrade-guide-4_XX.adoc files for every release line live on
main,
which holds the canonical history across all releases. A backport should
not carry
an upgrade-guide edit, so this note does not belong here.
It was also appended to the end of the file, which placed it under
"Upgrading Camel 4.17 to 4.18" rather than "Upgrading from 4.18.4 to
4.18.5".
The note is added to main's camel-4x-upgrade-guide-4_18.adoc, in the correct
section, by #25734.
Co-authored-by: Claude Opus 5 (1M context) <[email protected]>
---
.../ROOT/pages/camel-4x-upgrade-guide-4_18.adoc | 21 ---------------------
1 file changed, 21 deletions(-)
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 a66416405067..ea02914342af 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
@@ -1642,24 +1642,3 @@ that resolve outside the configured directory are
rejected.
If `downloadFileName` is configured with an expression (i.e. it contains `$`),
the local
path is built by that expression as before and is not subject to this check.
-
-=== camel-spring-redis - the default serializer applies a deserialization
filter
-
-The default serializer, `JdkSerializationRedisSerializer`, now installs a
-`java.io.ObjectInputFilter` while reading Redis payloads. Previously no filter
was applied at all.
-This affects both the consumer, which deserializes the payload of every
message published to the
-subscribed channels, and the producer read commands, which deserialize the
values stored in Redis.
-
-When no explicit pattern is configured, the JVM-wide `jdk.serialFilter` is
honoured if set,
-otherwise a conservative default allow-list is applied (it permits standard
Java and Apache Camel
-types and denies `java.net.**`). Routes that exchange classes outside that
allow-list must widen it
-through the new `deserializationFilter` endpoint option, for example:
-
-[source,java]
-----
-from("spring-redis://localhost:6379?command=SUBSCRIBE&channels=myChannel"
- + "&deserializationFilter=com.example.model.**;java.**;!*")
-----
-
-Setting the `serializer` option to a custom `RedisSerializer` bypasses the
filter entirely, since
-Camel then no longer controls how the payload is read.
