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 ce94e3be0aae Update component.adoc (#22508)
ce94e3be0aae is described below
commit ce94e3be0aae0c5c785b75d3ddd720e115ada0fc
Author: Andreas Jonsson <[email protected]>
AuthorDate: Thu Apr 9 11:21:23 2026 +0200
Update component.adoc (#22508)
This note references itself: the component page is the same page we are
already on.
---
docs/user-manual/modules/ROOT/pages/component.adoc | 5 -----
1 file changed, 5 deletions(-)
diff --git a/docs/user-manual/modules/ROOT/pages/component.adoc
b/docs/user-manual/modules/ROOT/pages/component.adoc
index 34c74f28c7f3..3e6489605e87 100644
--- a/docs/user-manual/modules/ROOT/pages/component.adoc
+++ b/docs/user-manual/modules/ROOT/pages/component.adoc
@@ -16,11 +16,6 @@ For the URI given in the above example, the `CamelContext`
object would map the
The parameter to `getEndpoint()` is a URI. The URI _scheme_ (that is,
the part before `:`) specifies the name of a component. Internally, the
`CamelContext` object maintains a mapping from the names of components to
`Component` objects.
-[NOTE]
-====
-Our documentation contains an in-depth overview of the
xref:manual::component.adoc[Component] if you want to learn more about it,
including important details necessary to write your own.
-====
-
== Configuring Component Options
Camel components are configured on two separate levels:
