This is an automated email from the ASF dual-hosted git repository.
oscerd 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 df85d15a3dcb CAMEL-25375: Upgrade guide - move the 4.18 notes of the
fixes that ship in 4.18.6 (#27713)
df85d15a3dcb is described below
commit df85d15a3dcbc5df014f0e9eb8baf78ca3209c21
Author: Andrea Cosentino <[email protected]>
AuthorDate: Mon Oct 12 10:36:14 2026 +0200
CAMEL-25375: Upgrade guide - move the 4.18 notes of the fixes that ship in
4.18.6 (#27713)
The camel-spring-ws (CAMEL-25340) and camel-undertow (CAMEL-25375)
backports merged after release/4.18.5 was cut, so they ship in 4.18.6; their
notes move verbatim from the 4.18.4-to-4.18.5 section to a new 4.18.5-to-4.18.6
section.
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
Signed-off-by: Andrea Cosentino <[email protected]>
---
.../ROOT/pages/camel-4x-upgrade-guide-4_18.adoc | 62 +++++++++++-----------
1 file changed, 32 insertions(+), 30 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 b0efcb6e391b..90adf6aa337e 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
@@ -11,7 +11,7 @@ Note that manual migration is still required.
See the xref:camel-upgrade-recipes-tool.adoc[documentation] page for details.
====
-== Upgrading from 4.18.4 to 4.18.5
+== Upgrading from 4.18.5 to 4.18.6
=== camel-netty-http - the roles of a security constraint are matched by role
name
@@ -20,6 +20,37 @@ user is now accepted only when one of their roles is equal
to one of those names
whitespace around each name and blank entries are ignored, and a value of `*`
still accepts any role. A roles value
that uses another separator, such as `admin;guest` or `admin guest`, must be
changed to `admin,guest`.
+=== camel-spring-ws - internal Camel headers are no longer written into SOAP
headers
+
+The default `messageFilter` of the `spring-ws` component,
`BasicMessageFilter`, now applies the endpoint's
+`headerFilterStrategy` before it writes a message header into the SOAP header,
both on the request sent by the
+producer and on the response returned by the consumer. With the default
`SpringWebserviceHeaderFilterStrategy`,
+message headers whose names start with `Camel` or `camel` (case-insensitively)
are no longer written into the SOAP
+header. Other message headers are written as before.
+
+A `BasicMessageFilter` created in application code applies a
`SpringWebserviceHeaderFilterStrategy` unless it is
+created with another strategy. A route that relies on the previous behaviour
can supply a custom
+`headerFilterStrategy` on the `spring-ws` endpoint.
+
+=== camel-undertow - WebSocket endpoints apply the security provider, allowed
roles and handlers
+
+WebSocket endpoints (`ws://` and `wss://`) now apply the
`UndertowSecurityProvider` (the `securityConfiguration` or
+`securityProvider` option), the `allowedRoles` option, and the `handlers` and
`accessLog` options, as HTTP endpoints
+do. Previously these options had no effect on WebSocket endpoints. They apply
to the upgrade request: a client that
+the security provider rejects, or that connects to an endpoint with
`allowedRoles` but no security provider, now gets
+the same status code as on an HTTP endpoint (for example `403`) and no
connection is opened. The headers that the
+security provider adds are set on the exchanges of the connection.
+
+All the endpoints of a WebSocket path share its connections. The settings of
the consumer apply to the path,
+including the messages sent by producers on that path, and keep applying while
the consumer is stopped; a path that
+only has producers applies their settings. A connection that was opened before
these settings applied does not
+receive the messages of the producers, and it is closed when it sends a
message.
+
+A WebSocket client that connected without satisfying the configured security
provider or allowed roles is now
+rejected: it must authenticate, or the option must be removed from the
WebSocket endpoint.
+
+== Upgrading from 4.18.4 to 4.18.5
+
=== camel-azure-eventhubs
The producer now leaves the Camel-internal headers (`Camel*`) out of the
`EventData` application properties by
@@ -73,18 +104,6 @@ Other SOAP response header attributes and elements are
mapped as before, and the
available in the `CamelSpringWebserviceSoapHeader` header. A route that relies
on the previous behaviour can supply a
custom `headerFilterStrategy` on the `spring-ws` endpoint.
-=== camel-spring-ws - internal Camel headers are no longer written into SOAP
headers
-
-The default `messageFilter` of the `spring-ws` component,
`BasicMessageFilter`, now applies the endpoint's
-`headerFilterStrategy` before it writes a message header into the SOAP header,
both on the request sent by the
-producer and on the response returned by the consumer. With the default
`SpringWebserviceHeaderFilterStrategy`,
-message headers whose names start with `Camel` or `camel` (case-insensitively)
are no longer written into the SOAP
-header. Other message headers are written as before.
-
-A `BasicMessageFilter` created in application code applies a
`SpringWebserviceHeaderFilterStrategy` unless it is
-created with another strategy. A route that relies on the previous behaviour
can supply a custom
-`headerFilterStrategy` on the `spring-ws` endpoint.
-
=== camel-http-common, camel-platform-http-vertx - fileNameExtWhitelist
entries are matched exactly
`fileNameExtWhitelist` is now checked the same way everywhere, by one shared
check in `camel-http-base`. Two
@@ -403,23 +422,6 @@ coap://0.0.0.0:5683/my/resource?muteException=false
For the Rest DSL, set it with
`restConfiguration().endpointProperty("muteException", "false")`.
-=== camel-undertow - WebSocket endpoints apply the security provider, allowed
roles and handlers
-
-WebSocket endpoints (`ws://` and `wss://`) now apply the
`UndertowSecurityProvider` (the `securityConfiguration` or
-`securityProvider` option), the `allowedRoles` option, and the `handlers` and
`accessLog` options, as HTTP endpoints
-do. Previously these options had no effect on WebSocket endpoints. They apply
to the upgrade request: a client that
-the security provider rejects, or that connects to an endpoint with
`allowedRoles` but no security provider, now gets
-the same status code as on an HTTP endpoint (for example `403`) and no
connection is opened. The headers that the
-security provider adds are set on the exchanges of the connection.
-
-All the endpoints of a WebSocket path share its connections. The settings of
the consumer apply to the path,
-including the messages sent by producers on that path, and keep applying while
the consumer is stopped; a path that
-only has producers applies their settings. A connection that was opened before
these settings applied does not
-receive the messages of the producers, and it is closed when it sends a
message.
-
-A WebSocket client that connected without satisfying the configured security
provider or allowed roles is now
-rejected: it must authenticate, or the option must be removed from the
WebSocket endpoint.
-
== Upgrading from 4.18.3 to 4.18.4
=== camel-core - Multicast EIP honors UseOriginalAggregationStrategy
