This is an automated email from the ASF dual-hosted git repository.
davsclaus 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 6afe9409a1cf CAMEL-23128: fix broken links (#21708)
6afe9409a1cf is described below
commit 6afe9409a1cfd8714aa120450844babc9b4c4230
Author: Gaëlle Fournier <[email protected]>
AuthorDate: Thu Mar 5 09:49:54 2026 +0100
CAMEL-23128: fix broken links (#21708)
---
.../camel-jetty/src/main/docs/jetty-component.adoc | 34 +++++++++++++++++++--
.../camel-spring/src/main/docs/spring-summary.adoc | 3 --
.../src/main/docs/undertow-component.adoc | 35 ++++++++++++++++++++--
3 files changed, 65 insertions(+), 7 deletions(-)
diff --git a/components/camel-jetty/src/main/docs/jetty-component.adoc
b/components/camel-jetty/src/main/docs/jetty-component.adoc
index 79dd74ac2742..2558616210ee 100644
--- a/components/camel-jetty/src/main/docs/jetty-component.adoc
+++ b/components/camel-jetty/src/main/docs/jetty-component.adoc
@@ -92,10 +92,40 @@ the numerical IP address of this interface should be used
as the host.
If you need to expose a Jetty endpoint on all network interfaces, the
`0.0.0.0` address should be used.
-To listen across an entire URI prefix, see
-xref:manual:faq:how-do-i-let-jetty-match-wildcards.adoc[How do I let Jetty
match wildcards].
+To listen across an entire URI prefix, see below.
====
+=== How do I let Jetty match wildcards?
+
+By default xref:components::jetty-component.adoc[Jetty] will only match on
exact uri's. But
+you can instruct Jetty to match prefixes. For example:
+
+[source,java]
+----
+from("jetty://0.0.0.0:8123/foo").to("mock:foo");
+----
+
+In the route above xref:components::jetty-component.adoc[Jetty] will only
match if the uri is
+an exact match, so it will match if you enter
+`\http://0.0.0.0:8123/foo` but not match if you do
+`\http://0.0.0.0:8123/foo/bar`.
+
+So if you want to enable wildcard matching you do as follows:
+
+[source,java]
+----
+from("jetty://0.0.0.0:8123/foo?matchOnUriPrefix=true").to("mock:foo");
+----
+
+So now Jetty matches any endpoints with starts with `foo`.
+
+To match *any* endpoint you can do:
+
+[source,java]
+----
+from("jetty://0.0.0.0:8123?matchOnUriPrefix=true").to("mock:foo");
+----
+
=== Servlets
If you actually want to expose routes by HTTP and already have a
diff --git
a/components/camel-spring-parent/camel-spring/src/main/docs/spring-summary.adoc
b/components/camel-spring-parent/camel-spring/src/main/docs/spring-summary.adoc
index aa7c86f90664..9b4a9d251b0f 100644
---
a/components/camel-spring-parent/camel-spring/src/main/docs/spring-summary.adoc
+++
b/components/camel-spring-parent/camel-spring/src/main/docs/spring-summary.adoc
@@ -398,9 +398,6 @@ the above example), then you can refer to the component
using
SpringCamelContext lazily fetching components from the spring context
for the scheme name you use for Endpoint URIs.
-For more details, see
xref:manual:faq:how-do-i-configure-endpoints.adoc[Configuring
-Endpoints and Components].
-
== CamelContextAware
If you want the `CamelContext` to be injected
diff --git a/components/camel-undertow/src/main/docs/undertow-component.adoc
b/components/camel-undertow/src/main/docs/undertow-component.adoc
index f627611dd5f9..7c9daea911e7 100644
--- a/components/camel-undertow/src/main/docs/undertow-component.adoc
+++ b/components/camel-undertow/src/main/docs/undertow-component.adoc
@@ -85,13 +85,44 @@ the numerical IP address of this interface should be used
as the host.
If you need to expose an Undertow endpoint on all network interfaces, the
`0.0.0.0` address should be used.
-To listen across an entire URI prefix, see
-xref:manual:faq:how-do-i-let-jetty-match-wildcards.adoc[How do I let Jetty
match wildcards?].
+To listen across an entire URI prefix, see below.
If you actually want to expose routes by HTTP and already have a
Servlet, you should instead refer to the
xref:servlet-component.adoc[Servlet Transport].
+
+=== How do I let Jetty match wildcards?
+
+By default, Jetty will only match on exact uri's. But you can instruct Jetty
to match prefixes. For example:
+
+[source,java]
+----
+from("jetty://0.0.0.0:8123/foo").to("mock:foo");
+----
+
+In the route above Jetty will only match if the uri is
+an exact match, so it will match if you enter
+`\http://0.0.0.0:8123/foo` but not match if you do
+`\http://0.0.0.0:8123/foo/bar`.
+
+So if you want to enable wildcard matching you need to set
`matchOnUriPrefix=true` as follows:
+
+[source,java]
+----
+from("jetty://0.0.0.0:8123/foo?matchOnUriPrefix=true").to("mock:foo");
+----
+
+So now Jetty matches any endpoints with starts with `foo`.
+
+To match *any* endpoint you can remove the prefix so it will match anything
from the root:
+
+[source,java]
+----
+from("jetty://0.0.0.0:8123?matchOnUriPrefix=true").to("mock:foo");
+----
+
+
=== Security provider
To plug in a security provider for endpoint authentication, implement SPI
interface
