This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch camel-4.14.x
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/camel-4.14.x by this push:
new 0115b3dcaf7 CAMEL-22413: Explain the situation to use Kamelet EIP in
the catalog (#19173)
0115b3dcaf7 is described below
commit 0115b3dcaf7ed41888915fb6a2e572e7cc5bf283
Author: Tomo Igarashi <[email protected]>
AuthorDate: Tue Sep 16 01:01:45 2025 -0400
CAMEL-22413: Explain the situation to use Kamelet EIP in the catalog
(#19173)
---
.../resources/org/apache/camel/catalog/models/kamelet.json | 2 +-
.../resources/org/apache/camel/catalog/schemas/camel-spring.xsd | 6 +++++-
.../resources/org/apache/camel/catalog/schemas/camel-xml-io.xsd | 6 +++++-
.../src/main/docs/modules/eips/pages/kamelet-eip.adoc | 2 +-
.../resources/META-INF/org/apache/camel/model/kamelet.json | 2 +-
.../src/main/java/org/apache/camel/model/KameletDefinition.java | 6 +++++-
6 files changed, 18 insertions(+), 6 deletions(-)
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/models/kamelet.json
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/models/kamelet.json
index a533e51d08c..a192029bd82 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/models/kamelet.json
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/models/kamelet.json
@@ -3,7 +3,7 @@
"kind": "model",
"name": "kamelet",
"title": "Kamelet",
- "description": "To call Kamelets in special situations",
+ "description": "To call Kamelets in special situations. By default,
calling kamelets should be done as endpoints with the kamelet component, such
as to(kamelet:mykamelet). When a Kamelet is designed for a special use-case
such as aggregating messages, and returning a response message only when a
group of aggregated messages is completed. In other words, kamelet does not
return a response message for every incoming message. In special situations
like these, then you must use this Kame [...]
"deprecated": false,
"label": "eip,routing",
"javaType": "org.apache.camel.model.KameletDefinition",
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/schemas/camel-spring.xsd
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/schemas/camel-spring.xsd
index ee0cea5e937..3d2c208a4e2 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/schemas/camel-spring.xsd
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/schemas/camel-spring.xsd
@@ -908,7 +908,11 @@ JTA based transactional error handler (requires camel-jta).
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To call Kamelets in special situations
+To call Kamelets in special situations. By default, calling kamelets should be
done as endpoints with the kamelet
+component, such as to(kamelet:mykamelet). When a Kamelet is designed for a
special use-case such as aggregating
+messages, and returning a response message only when a group of aggregated
messages is completed. In other words,
+kamelet does not return a response message for every incoming message. In
special situations like these, then you must
+use this Kamelet EIP instead of using the kamelet component.
]]>
</xs:documentation>
</xs:annotation>
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/schemas/camel-xml-io.xsd
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/schemas/camel-xml-io.xsd
index ecf208c62b4..28f7894acec 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/schemas/camel-xml-io.xsd
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/schemas/camel-xml-io.xsd
@@ -854,7 +854,11 @@ JTA based transactional error handler (requires camel-jta).
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To call Kamelets in special situations
+To call Kamelets in special situations. By default, calling kamelets should be
done as endpoints with the kamelet
+component, such as to(kamelet:mykamelet). When a Kamelet is designed for a
special use-case such as aggregating
+messages, and returning a response message only when a group of aggregated
messages is completed. In other words,
+kamelet does not return a response message for every incoming message. In
special situations like these, then you must
+use this Kamelet EIP instead of using the kamelet component.
]]>
</xs:documentation>
</xs:annotation>
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 69abc78643b..8ef0813ce17 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
@@ -1,7 +1,7 @@
= Kamelet EIP
:doctitle: Kamelet
:shortname: kamelet
-:description: To call Kamelets in special situations
+:description: To call Kamelets in special situations. By default, calling
kamelets should be done as endpoints with the kamelet component, such as
to(kamelet:mykamelet). When a Kamelet is designed for a special use-case such
as aggregating messages, and returning a response message only when a group of
aggregated messages is completed. In other words, kamelet does not return a
response message for every incoming message. In special situations like these,
then you must use this Kamelet EI [...]
:since:
:supportlevel: Stable
:tabs-sync-option:
diff --git
a/core/camel-core-model/src/generated/resources/META-INF/org/apache/camel/model/kamelet.json
b/core/camel-core-model/src/generated/resources/META-INF/org/apache/camel/model/kamelet.json
index a533e51d08c..a192029bd82 100644
---
a/core/camel-core-model/src/generated/resources/META-INF/org/apache/camel/model/kamelet.json
+++
b/core/camel-core-model/src/generated/resources/META-INF/org/apache/camel/model/kamelet.json
@@ -3,7 +3,7 @@
"kind": "model",
"name": "kamelet",
"title": "Kamelet",
- "description": "To call Kamelets in special situations",
+ "description": "To call Kamelets in special situations. By default,
calling kamelets should be done as endpoints with the kamelet component, such
as to(kamelet:mykamelet). When a Kamelet is designed for a special use-case
such as aggregating messages, and returning a response message only when a
group of aggregated messages is completed. In other words, kamelet does not
return a response message for every incoming message. In special situations
like these, then you must use this Kame [...]
"deprecated": false,
"label": "eip,routing",
"javaType": "org.apache.camel.model.KameletDefinition",
diff --git
a/core/camel-core-model/src/main/java/org/apache/camel/model/KameletDefinition.java
b/core/camel-core-model/src/main/java/org/apache/camel/model/KameletDefinition.java
index 34aa5cbd203..0c555b63ddd 100644
---
a/core/camel-core-model/src/main/java/org/apache/camel/model/KameletDefinition.java
+++
b/core/camel-core-model/src/main/java/org/apache/camel/model/KameletDefinition.java
@@ -27,7 +27,11 @@ import jakarta.xml.bind.annotation.XmlRootElement;
import org.apache.camel.spi.Metadata;
/**
- * To call Kamelets in special situations
+ * To call Kamelets in special situations. By default, calling kamelets should
be done as endpoints with the kamelet
+ * component, such as to("kamelet:mykamelet"). When a Kamelet is designed for
a special use-case such as aggregating
+ * messages, and returning a response message only when a group of aggregated
messages is completed. In other words,
+ * kamelet does not return a response message for every incoming message. In
special situations like these, then you
+ * must use this Kamelet EIP instead of using the kamelet component.
*/
@Metadata(label = "eip,routing")
@XmlRootElement(name = "kamelet")
