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 d326ff38231b chore: escape attribute references in the 4.23 upgrade
guide
d326ff38231b is described below
commit d326ff38231ba338aa512358c91da5f717ecbb4b
Author: Claus Ibsen <[email protected]>
AuthorDate: Wed Sep 23 15:13:21 2026 +0200
chore: escape attribute references in the 4.23 upgrade guide
The inline `${body}` and `/stock/{sku}` were read by Asciidoctor as
attribute references, so the camel-website build warned about a missing
attribute for each. Wrap both in the +...+ passthrough the same file
already uses for `+/users/{id}+` and `+platform-http:/greeting/{name}+`.
Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
Signed-off-by: Claus Ibsen <[email protected]>
---
docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_23.adoc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_23.adoc
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_23.adoc
index 1c5679137d41..1cc7bcf85852 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_23.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_23.adoc
@@ -22,7 +22,7 @@ OAuth client credentials token caching now distinguishes
profiles by client secr
`${ }` may now hold a predicate, as the braces do in Jakarta EL, Groovy and a
JavaScript template:
`${body != null && body.size() > 0}` answers whether it matches, instead of
being refused with
_Operators go outside the function_. The form with the operators outside the
braces
-(`${body} != null && ${body.size()} > 0`) means the same and is unchanged, and
the ternary keeps
+(`+${body} != null && ${body.size()} > 0+`) means the same and is unchanged,
and the ternary keeps
working as before.
An operator counts only when whitespace surrounds it outside quotes, so a name
such as
@@ -2362,7 +2362,7 @@ text itself is resolved as before, and a returned value
that happens to start wi
=== camel-platform-http-vertx - a path parameter wins over an incoming header
of the same name
-A REST endpoint with a path parameter, `/stock/{sku}`, sets the header `sku`
from the path. When the request also
+A REST endpoint with a path parameter, `+/stock/{sku}+`, sets the header `sku`
from the path. When the request also
carried an HTTP header of that name, the two were merged and `${header.sku}`
was a `List` such as `[X, CAMEL-MUG]`,
so a route that read it failed even when the path value was correct. The value
from the path is used now; a query
parameter may still repeat and is still collected into a list.
