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 1696ae8ecf7b CAMEL-25895: docs - upgrade-guide notes for the Swift
header rename on the 4.18.6 and 4.22.3 lines (#28850)
1696ae8ecf7b is described below
commit 1696ae8ecf7b9f880a17051d7daa0d0056c5fd86
Author: Zineb BENDHIBA <[email protected]>
AuthorDate: Mon Nov 2 11:51:51 2026 +0100
CAMEL-25895: docs - upgrade-guide notes for the Swift header rename on the
4.18.6 and 4.22.3 lines (#28850)
Co-Authored-By: Claude Opus 5 <[email protected]>
---
.../ROOT/pages/camel-4x-upgrade-guide-4_18.adoc | 32 +++++++++++++++++++++-
.../ROOT/pages/camel-4x-upgrade-guide-4_21.adoc | 2 +-
.../ROOT/pages/camel-4x-upgrade-guide-4_22.adoc | 30 ++++++++++++++++++++
3 files changed, 62 insertions(+), 2 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 14cdbc2d4672..7348254e86fd 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
@@ -564,6 +564,36 @@ When `downloadFileName` is fully dynamic and has no static
directory prefix (for
`downloadFileName=${file:name}`), a relative destination must stay within the
working directory. An absolute
destination that comes from the route's own expression is not confined.
+=== camel-openstack - the remaining Swift header constants follow the Camel
naming convention
+
+The four remaining Exchange header constants of `SwiftConstants` have been
renamed to follow the Camel naming
+convention used by the rest of the component, completing the rename done in
4.18.3. The Java field names are
+unchanged; only the header string values have changed.
+
+[options="header"]
+|===
+| Constant | Previous value | New value
+| `SwiftConstants.CONTAINER_METADATA_PREFIX` | `X-Container-Meta-` |
`CamelOpenstackSwiftContainerMetadata`
+| `SwiftConstants.VERSIONS_LOCATION` | `X-Versions-Location` |
`CamelOpenstackSwiftVersionsLocation`
+| `SwiftConstants.CONTAINER_READ` | `X-Container-Read` |
`CamelOpenstackSwiftContainerRead`
+| `SwiftConstants.CONTAINER_WRITE` | `X-Container-Write` |
`CamelOpenstackSwiftContainerWrite`
+|===
+
+The previous values were kept in 4.18.3 on the understanding that they were
part of the Swift HTTP contract. They are
+not: the container producer passes the values to the openstack4j
`CreateUpdateContainerOptions`, which builds the
+`X-Container-Meta-`, `X-Versions-Location`, `X-Container-Read` and
`X-Container-Write` names of the Swift request
+itself. The request Camel sends to Swift is therefore unchanged by this rename.
+
+Routes that reference the constants symbolically (for example
`setHeader(SwiftConstants.CONTAINER_READ, ...)`)
+continue to work without changes. Routes that set one of these headers by its
literal string value (for example
+`setHeader("X-Container-Read", ...)` in an XML or YAML route) must be updated
to the new value
+(`setHeader("CamelOpenstackSwiftContainerRead", ...)`); the previous names are
no longer read.
+
+The generated Endpoint DSL header accessors on the Swift `HeaderNameBuilder`
are renamed accordingly
+(`xContainerMeta()` -> `openstackSwiftContainerMetadata()`,
`xVersionsLocation()` ->
+`openstackSwiftVersionsLocation()`, `xContainerRead()` ->
`openstackSwiftContainerRead()`, `xContainerWrite()` ->
+`openstackSwiftContainerWrite()`).
+
== Upgrading from 4.18.4 to 4.18.5
=== camel-azure-eventhubs
@@ -1813,7 +1843,7 @@ their previous values (`X-Container-Meta-`,
`X-Versions-Location`,
`X-Container-Read`, `X-Container-Write`) in this release.
NOTE: These four constants have since been renamed to follow the Camel naming
-convention; see CAMEL-25895 for the releases that carry the change. They are
+convention, in 4.18.6, 4.22.3 and 4.24.0 (CAMEL-25895). They are
Exchange header keys only: openstack4j builds the `X-Container-*` wire headers
itself from `CreateUpdateContainerOptions`, so the Camel header name never
reaches Swift.
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_21.adoc
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_21.adoc
index ce69b6289e00..747e1901734e 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_21.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_21.adoc
@@ -1793,7 +1793,7 @@ their previous values (`X-Container-Meta-`,
`X-Versions-Location`,
`X-Container-Read`, `X-Container-Write`) in this release.
NOTE: These four constants have since been renamed to follow the Camel naming
-convention; see CAMEL-25895 for the releases that carry the change. They are
+convention, in 4.18.6, 4.22.3 and 4.24.0 (CAMEL-25895). They are
Exchange header keys only: openstack4j builds the `X-Container-*` wire headers
itself from `CreateUpdateContainerOptions`, so the Camel header name never
reaches Swift.
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 da7921f8afd8..1dcd49a6d72e 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
@@ -415,6 +415,36 @@ When `downloadFileName` is fully dynamic and has no static
directory prefix (for
`downloadFileName=${file:name}`), a relative destination must stay within the
working directory. An absolute
destination that comes from the route's own expression is not confined.
+=== camel-openstack - the remaining Swift header constants follow the Camel
naming convention
+
+The four remaining Exchange header constants of `SwiftConstants` have been
renamed to follow the Camel naming
+convention used by the rest of the component, completing the rename done in
4.21. The Java field names are
+unchanged; only the header string values have changed.
+
+[options="header"]
+|===
+| Constant | Previous value | New value
+| `SwiftConstants.CONTAINER_METADATA_PREFIX` | `X-Container-Meta-` |
`CamelOpenstackSwiftContainerMetadata`
+| `SwiftConstants.VERSIONS_LOCATION` | `X-Versions-Location` |
`CamelOpenstackSwiftVersionsLocation`
+| `SwiftConstants.CONTAINER_READ` | `X-Container-Read` |
`CamelOpenstackSwiftContainerRead`
+| `SwiftConstants.CONTAINER_WRITE` | `X-Container-Write` |
`CamelOpenstackSwiftContainerWrite`
+|===
+
+The previous values were kept in 4.21 on the understanding that they were part
of the Swift HTTP contract. They are
+not: the container producer passes the values to the openstack4j
`CreateUpdateContainerOptions`, which builds the
+`X-Container-Meta-`, `X-Versions-Location`, `X-Container-Read` and
`X-Container-Write` names of the Swift request
+itself. The request Camel sends to Swift is therefore unchanged by this rename.
+
+Routes that reference the constants symbolically (for example
`setHeader(SwiftConstants.CONTAINER_READ, ...)`)
+continue to work without changes. Routes that set one of these headers by its
literal string value (for example
+`setHeader("X-Container-Read", ...)` in an XML or YAML route) must be updated
to the new value
+(`setHeader("CamelOpenstackSwiftContainerRead", ...)`); the previous names are
no longer read.
+
+The generated Endpoint DSL header accessors on the Swift `HeaderNameBuilder`
are renamed accordingly
+(`xContainerMeta()` -> `openstackSwiftContainerMetadata()`,
`xVersionsLocation()` ->
+`openstackSwiftVersionsLocation()`, `xContainerRead()` ->
`openstackSwiftContainerRead()`, `xContainerWrite()` ->
+`openstackSwiftContainerWrite()`).
+
== Upgrading from 4.22.1 to 4.22.2
=== camel-lra - only an LRA hosted by the configured coordinator is joined
