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
commit d0cacfe3bdc303ec64e93aff583e099ad80c5488
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Thu Sep 23 17:09:56 2021 +0200
CAMEL-16861: Cleanup and update EIP docs
---
.../main/docs/modules/eips/pages/kamelet-eip.adoc | 20 +++++++++++---------
1 file changed, 11 insertions(+), 9 deletions(-)
diff --git
a/core/camel-core-engine/src/main/docs/modules/eips/pages/kamelet-eip.adoc
b/core/camel-core-engine/src/main/docs/modules/eips/pages/kamelet-eip.adoc
index 8a6e8cf..1355e9e 100644
--- a/core/camel-core-engine/src/main/docs/modules/eips/pages/kamelet-eip.adoc
+++ b/core/camel-core-engine/src/main/docs/modules/eips/pages/kamelet-eip.adoc
@@ -11,6 +11,13 @@ hiding all the low level details about how those connections
are implemented.
The Kamelet EIP allows to call Kamelets (route templates).
When calling a Kamelet you may just refer to the name (template id) of the
Kamelet in the EIP as shown below:
+== Options
+// eip options: START
+include::partial$eip-options.adoc[]
+// eip options: END
+
+== Using Kamelet EIP
+
[source,java]
----
from("direct:start")
@@ -18,15 +25,15 @@ from("direct:start")
.to("mock:result");
----
+And in XML
+
[source,xml]
----
-<camelContext xmlns="http://camel.apache.org/schema/spring";>
- <route>
+<route>
<from uri="direct:start"/>
<kamelet name="foo"/>
<to uri="mock:result"/>
- </route>
-</camelContext>
+</route>
----
Camel will then, when starting:
@@ -34,11 +41,6 @@ Camel will then, when starting:
* lookup the route template with the given id (i.e. foo) from the Camel context
* create a new route based on the route template
-== Options
-// eip options: START
-include::partial$eip-options.adoc[]
-// eip options: END
-
== Dependency
The implementation of the Kamelet EIP is located in the `camel-kamelet` JAR,
so you should add the following dependency:
