This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch camel-4.22.x
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/camel-4.22.x by this push:
new 0efe88ea48d7 [backport camel-4.22.x] chore(docs): escape wildcards in
monospace so pages render valid HTML (#26380) (#26381)
0efe88ea48d7 is described below
commit 0efe88ea48d701a11b4e4c91be6f1e7751478b30
Author: Adriano Machado <[email protected]>
AuthorDate: Mon Sep 14 00:34:24 2026 -0400
[backport camel-4.22.x] chore(docs): escape wildcards in monospace so pages
render valid HTML (#26380) (#26381)
A * inside a single-backtick span is still parsed as a formatting mark,
so spans such as `mail.smtp.*` or `!java.net.**;java.**;...;!*` pair up
with a later * and produce mis-nested HTML like <code>…<strong></code>.
The website's HTML-to-Markdown step then loses article.doc and skips the
page, so the components/4.22.x .md mirror returns 404
(apache/camel-website#1746).
Use literal monospace (`+…+`) for those spans in the component docs
published from this branch: mail, leveldb, ai-tool, mcp-server, mdc and
yaml-dsl. leveldb is not on main (the component was removed there), so
its change is new in this backport. Catalog doc copies are synced.
_Claude Code on behalf of Adriano Machado (@ammachado)_
_This was generated by an AI agent and may contain inaccuracies.
Please verify before relying on it._
---
.../org/apache/camel/catalog/docs/ai-tool-component.adoc | 2 +-
.../resources/org/apache/camel/catalog/docs/leveldb.adoc | 6 +++---
.../resources/org/apache/camel/catalog/docs/mail-component.adoc | 4 ++--
.../resources/org/apache/camel/catalog/docs/mcp-server.adoc | 8 ++++----
.../generated/resources/org/apache/camel/catalog/docs/mdc.adoc | 4 ++--
.../resources/org/apache/camel/catalog/docs/yaml-dsl.adoc | 2 +-
.../camel-ai/camel-ai-tool/src/main/docs/ai-tool-component.adoc | 2 +-
.../camel-ai/camel-mcp-server/src/main/docs/mcp-server.adoc | 8 ++++----
components/camel-leveldb/src/main/docs/leveldb.adoc | 6 +++---
components/camel-mail/src/main/docs/mail-component.adoc | 4 ++--
components/camel-mdc/src/main/docs/mdc.adoc | 4 ++--
dsl/camel-yaml-dsl/camel-yaml-dsl/src/main/docs/yaml-dsl.adoc | 2 +-
12 files changed, 26 insertions(+), 26 deletions(-)
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/ai-tool-component.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/ai-tool-component.adoc
index 7d136fc59601..fdab3a0a6d68 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/ai-tool-component.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/ai-tool-component.adoc
@@ -147,7 +147,7 @@ YAML::
=== Complex Parameters with argSchema
-Use `argSchema` when the flat `parameter.*` syntax is not expressive enough
for nested objects, arrays, or other advanced JSON Schema constructs.
`argSchema` is mutually exclusive with `parameter.*`.
+Use `argSchema` when the flat `+parameter.*+` syntax is not expressive enough
for nested objects, arrays, or other advanced JSON Schema constructs.
`argSchema` is mutually exclusive with `+parameter.*+`.
[tabs]
====
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/leveldb.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/leveldb.adoc
index 5c517b359607..ede7db023346 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/leveldb.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/leveldb.adoc
@@ -74,12 +74,12 @@ used then the `maximumRedeliveries` option must also be
provided.
|`deserializationFilter` |String |A deserialization filter used when
deserializing exchange data from the LevelDB store. The filter uses the
standard Java `ObjectInputFilter` pattern syntax. By default, the filter
-is set to `!java.net.**;java.**;org.apache.camel.**;!*`, which denies
-classes under `java.net.*` (whose `hashCode`/`equals` methods perform
+is set to `+!java.net.**;java.**;org.apache.camel.**;!*+`, which denies
+classes under `+java.net.*+` (whose `hashCode`/`equals` methods perform
network I/O) and otherwise allows Java platform classes and Apache Camel
classes. If your application stores custom objects, you can adjust this
filter to include additional packages
-(e.g., `!java.net.**;java.**;org.apache.camel.**;com.mycompany.**;!*`).
+(e.g., `+!java.net.**;java.**;org.apache.camel.**;com.mycompany.**;!*+`).
|=======================================================================
The `repositoryName` option must be provided. Then either the
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/mail-component.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/mail-component.adoc
index a614e7fd5e8a..71ff5a3698f9 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/mail-component.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/mail-component.adoc
@@ -899,11 +899,11 @@ For example, to provide a dynamic uuid in
`mail.smtp.from` (SMTP MAIL command):
NOTE: This is only supported when *not* using a custom `JavaMailSender`.
WARNING: This feature is *disabled by default* and must be explicitly enabled
with
-`useJavaMailSessionPropertiesFromHeaders=true`. The `mail.smtp.*` /
`mail.smtps.*` keys are a
+`useJavaMailSessionPropertiesFromHeaders=true`. The `+mail.smtp.*+` /
`+mail.smtps.*+` keys are a
Camel-internal namespace that is not filtered by any `HeaderFilterStrategy`,
so if these headers can
originate from data crossing a trust boundary (for example HTTP query
parameters, or JMS/Kafka
messages from untrusted producers) an attacker could weaken transport security
(such as
`mail.smtp.ssl.trust` or `mail.smtp.starttls.enable`) or redirect the SMTP
connection. Only enable
the option when these headers are set exclusively by trusted route logic, and
strip the namespace
-with `removeHeaders("mail.smtp.*", "mail.smtps.*")` before the producer when
bridging an untrusted
+with `+removeHeaders("mail.smtp.*", "mail.smtps.*")+` before the producer when
bridging an untrusted
source. See the xref:manual::security-model.adoc[Camel Security Model] for the
general pattern.
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/mcp-server.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/mcp-server.adoc
index 6b761dc26029..18655e9cee08 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/mcp-server.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/mcp-server.adoc
@@ -48,9 +48,9 @@ Engine resolution mirrors the platform-http engine: a bean of
type
`McpServerEngine` in the Camel registry wins; otherwise the engine is
discovered on the classpath. Other runtimes plug native engines through the
same SPI: on Quarkus the `camel-quarkus-mcp-server` extension serves through
-the Quarkiverse `quarkus-mcp-server` (configured via `quarkus.mcp.server.*`),
+the Quarkiverse `quarkus-mcp-server` (configured via `+quarkus.mcp.server.*+`),
and on Spring Boot the starter serves through the Spring AI MCP server
-(configured via `spring.ai.mcp.server.*`). Bridge behavior — tag selection,
+(configured via `+spring.ai.mcp.server.*+`). Bridge behavior — tag selection,
timeout, sanitization — is identical on every runtime and verified by a shared
conformance test kit.
@@ -120,8 +120,8 @@ camel.server.mcp-tags = crm,notify
camel.server.mcp-server-name = my-integration-app
----
-Tag patterns support wildcards: use `*` to expose all tagged tools, or a
-prefix pattern like `crm*` to expose all tags starting with `crm`:
+Tag patterns support wildcards: use `+*+` to expose all tagged tools, or a
+prefix pattern like `+crm*+` to expose all tags starting with `crm`:
On other runtimes, or when wiring programmatically, add the
`McpServerBridge` service to the CamelContext instead:
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/mdc.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/mdc.adoc
index 708d9ca4a8d0..fcaae53169ac 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/mdc.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/mdc.adoc
@@ -70,6 +70,6 @@ The configuration properties for the MDC component are:
|=======================================================================
|Option |Default |Description
|`camel.mdc.enabled`| false | Enable the MDC logging.
-|`camel.mdc.customExchangeHeaders` | | Provide the exchange headers you would
like to trace in MDC. Use `*` value as a wildcard to include more exchange
headers at once, for example `CAMEL_HTTP_*` or only the `*` to include all
available exchange headers.
-|`camel.mdc.customExchangeProperties` | | Provide the exchange properties you
would like to trace in MDC. Use `*` value as a wildcard to include more
exchange properties at once, for example `property_*` or only the `*` to
include all available exchange properties.
+|`camel.mdc.customExchangeHeaders` | | Provide the exchange headers you would
like to trace in MDC. Use `+*+` value as a wildcard to include more exchange
headers at once, for example `+CAMEL_HTTP_*+` or only the `+*+` to include all
available exchange headers.
+|`camel.mdc.customExchangeProperties` | | Provide the exchange properties you
would like to trace in MDC. Use `+*+` value as a wildcard to include more
exchange properties at once, for example `+property_*+` or only the `+*+` to
include all available exchange properties.
|=======================================================================
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/yaml-dsl.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/yaml-dsl.adoc
index 6773f8a975c4..e8d9b667269a 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/yaml-dsl.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/yaml-dsl.adoc
@@ -837,7 +837,7 @@ a simpler, more predictable schema structure. The classic
schema remains the def
=== Using the schemas with IDEs
The classic schema is registered in the https://www.schemastore.org/[JSON
Schema Store] and is automatically
-used by IDEs like VS Code and IntelliJ for files matching `*.camel.yaml` and
`*.camelk.yaml`.
+used by IDEs like VS Code and IntelliJ for files matching `+*.camel.yaml+` and
`+*.camelk.yaml+`.
To use the canonical schema instead, configure your IDE to point to the
canonical schema URL:
diff --git
a/components/camel-ai/camel-ai-tool/src/main/docs/ai-tool-component.adoc
b/components/camel-ai/camel-ai-tool/src/main/docs/ai-tool-component.adoc
index 7d136fc59601..fdab3a0a6d68 100644
--- a/components/camel-ai/camel-ai-tool/src/main/docs/ai-tool-component.adoc
+++ b/components/camel-ai/camel-ai-tool/src/main/docs/ai-tool-component.adoc
@@ -147,7 +147,7 @@ YAML::
=== Complex Parameters with argSchema
-Use `argSchema` when the flat `parameter.*` syntax is not expressive enough
for nested objects, arrays, or other advanced JSON Schema constructs.
`argSchema` is mutually exclusive with `parameter.*`.
+Use `argSchema` when the flat `+parameter.*+` syntax is not expressive enough
for nested objects, arrays, or other advanced JSON Schema constructs.
`argSchema` is mutually exclusive with `+parameter.*+`.
[tabs]
====
diff --git a/components/camel-ai/camel-mcp-server/src/main/docs/mcp-server.adoc
b/components/camel-ai/camel-mcp-server/src/main/docs/mcp-server.adoc
index 6b761dc26029..18655e9cee08 100644
--- a/components/camel-ai/camel-mcp-server/src/main/docs/mcp-server.adoc
+++ b/components/camel-ai/camel-mcp-server/src/main/docs/mcp-server.adoc
@@ -48,9 +48,9 @@ Engine resolution mirrors the platform-http engine: a bean of
type
`McpServerEngine` in the Camel registry wins; otherwise the engine is
discovered on the classpath. Other runtimes plug native engines through the
same SPI: on Quarkus the `camel-quarkus-mcp-server` extension serves through
-the Quarkiverse `quarkus-mcp-server` (configured via `quarkus.mcp.server.*`),
+the Quarkiverse `quarkus-mcp-server` (configured via `+quarkus.mcp.server.*+`),
and on Spring Boot the starter serves through the Spring AI MCP server
-(configured via `spring.ai.mcp.server.*`). Bridge behavior — tag selection,
+(configured via `+spring.ai.mcp.server.*+`). Bridge behavior — tag selection,
timeout, sanitization — is identical on every runtime and verified by a shared
conformance test kit.
@@ -120,8 +120,8 @@ camel.server.mcp-tags = crm,notify
camel.server.mcp-server-name = my-integration-app
----
-Tag patterns support wildcards: use `*` to expose all tagged tools, or a
-prefix pattern like `crm*` to expose all tags starting with `crm`:
+Tag patterns support wildcards: use `+*+` to expose all tagged tools, or a
+prefix pattern like `+crm*+` to expose all tags starting with `crm`:
On other runtimes, or when wiring programmatically, add the
`McpServerBridge` service to the CamelContext instead:
diff --git a/components/camel-leveldb/src/main/docs/leveldb.adoc
b/components/camel-leveldb/src/main/docs/leveldb.adoc
index 5c517b359607..ede7db023346 100644
--- a/components/camel-leveldb/src/main/docs/leveldb.adoc
+++ b/components/camel-leveldb/src/main/docs/leveldb.adoc
@@ -74,12 +74,12 @@ used then the `maximumRedeliveries` option must also be
provided.
|`deserializationFilter` |String |A deserialization filter used when
deserializing exchange data from the LevelDB store. The filter uses the
standard Java `ObjectInputFilter` pattern syntax. By default, the filter
-is set to `!java.net.**;java.**;org.apache.camel.**;!*`, which denies
-classes under `java.net.*` (whose `hashCode`/`equals` methods perform
+is set to `+!java.net.**;java.**;org.apache.camel.**;!*+`, which denies
+classes under `+java.net.*+` (whose `hashCode`/`equals` methods perform
network I/O) and otherwise allows Java platform classes and Apache Camel
classes. If your application stores custom objects, you can adjust this
filter to include additional packages
-(e.g., `!java.net.**;java.**;org.apache.camel.**;com.mycompany.**;!*`).
+(e.g., `+!java.net.**;java.**;org.apache.camel.**;com.mycompany.**;!*+`).
|=======================================================================
The `repositoryName` option must be provided. Then either the
diff --git a/components/camel-mail/src/main/docs/mail-component.adoc
b/components/camel-mail/src/main/docs/mail-component.adoc
index a614e7fd5e8a..71ff5a3698f9 100644
--- a/components/camel-mail/src/main/docs/mail-component.adoc
+++ b/components/camel-mail/src/main/docs/mail-component.adoc
@@ -899,11 +899,11 @@ For example, to provide a dynamic uuid in
`mail.smtp.from` (SMTP MAIL command):
NOTE: This is only supported when *not* using a custom `JavaMailSender`.
WARNING: This feature is *disabled by default* and must be explicitly enabled
with
-`useJavaMailSessionPropertiesFromHeaders=true`. The `mail.smtp.*` /
`mail.smtps.*` keys are a
+`useJavaMailSessionPropertiesFromHeaders=true`. The `+mail.smtp.*+` /
`+mail.smtps.*+` keys are a
Camel-internal namespace that is not filtered by any `HeaderFilterStrategy`,
so if these headers can
originate from data crossing a trust boundary (for example HTTP query
parameters, or JMS/Kafka
messages from untrusted producers) an attacker could weaken transport security
(such as
`mail.smtp.ssl.trust` or `mail.smtp.starttls.enable`) or redirect the SMTP
connection. Only enable
the option when these headers are set exclusively by trusted route logic, and
strip the namespace
-with `removeHeaders("mail.smtp.*", "mail.smtps.*")` before the producer when
bridging an untrusted
+with `+removeHeaders("mail.smtp.*", "mail.smtps.*")+` before the producer when
bridging an untrusted
source. See the xref:manual::security-model.adoc[Camel Security Model] for the
general pattern.
diff --git a/components/camel-mdc/src/main/docs/mdc.adoc
b/components/camel-mdc/src/main/docs/mdc.adoc
index 708d9ca4a8d0..fcaae53169ac 100644
--- a/components/camel-mdc/src/main/docs/mdc.adoc
+++ b/components/camel-mdc/src/main/docs/mdc.adoc
@@ -70,6 +70,6 @@ The configuration properties for the MDC component are:
|=======================================================================
|Option |Default |Description
|`camel.mdc.enabled`| false | Enable the MDC logging.
-|`camel.mdc.customExchangeHeaders` | | Provide the exchange headers you would
like to trace in MDC. Use `*` value as a wildcard to include more exchange
headers at once, for example `CAMEL_HTTP_*` or only the `*` to include all
available exchange headers.
-|`camel.mdc.customExchangeProperties` | | Provide the exchange properties you
would like to trace in MDC. Use `*` value as a wildcard to include more
exchange properties at once, for example `property_*` or only the `*` to
include all available exchange properties.
+|`camel.mdc.customExchangeHeaders` | | Provide the exchange headers you would
like to trace in MDC. Use `+*+` value as a wildcard to include more exchange
headers at once, for example `+CAMEL_HTTP_*+` or only the `+*+` to include all
available exchange headers.
+|`camel.mdc.customExchangeProperties` | | Provide the exchange properties you
would like to trace in MDC. Use `+*+` value as a wildcard to include more
exchange properties at once, for example `+property_*+` or only the `+*+` to
include all available exchange properties.
|=======================================================================
diff --git a/dsl/camel-yaml-dsl/camel-yaml-dsl/src/main/docs/yaml-dsl.adoc
b/dsl/camel-yaml-dsl/camel-yaml-dsl/src/main/docs/yaml-dsl.adoc
index 6773f8a975c4..e8d9b667269a 100644
--- a/dsl/camel-yaml-dsl/camel-yaml-dsl/src/main/docs/yaml-dsl.adoc
+++ b/dsl/camel-yaml-dsl/camel-yaml-dsl/src/main/docs/yaml-dsl.adoc
@@ -837,7 +837,7 @@ a simpler, more predictable schema structure. The classic
schema remains the def
=== Using the schemas with IDEs
The classic schema is registered in the https://www.schemastore.org/[JSON
Schema Store] and is automatically
-used by IDEs like VS Code and IntelliJ for files matching `*.camel.yaml` and
`*.camelk.yaml`.
+used by IDEs like VS Code and IntelliJ for files matching `+*.camel.yaml+` and
`+*.camelk.yaml+`.
To use the canonical schema instead, configure your IDE to point to the
canonical schema URL:
