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-kamelets.git
The following commit(s) were added to refs/heads/main by this push:
new a860778be chore: jms-apache-artemis-* take username and password, the
sink pools its connections, jms-pooled-apache-artemis-* are deprecated (#3162,
group 2) (#3169)
a860778be is described below
commit a860778be3a9a46db566e8a6f30fd41f940df385
Author: Claus Ibsen <[email protected]>
AuthorDate: Tue Nov 17 16:07:44 2026 +0100
chore: jms-apache-artemis-* take username and password, the sink pools its
connections, jms-pooled-apache-artemis-* are deprecated (#3162, group 2) (#3169)
jms-apache-artemis-sink and jms-apache-artemis-source get the username and
password options. The sink also sends through a pooled-jms connection pool,
with the three pool options of the pooled variant, instead of opening a
connection per message. jms-pooled-apache-artemis-sink and
jms-pooled-apache-artemis-source keep working, unchanged, with the support
level Deprecated and a description and doc note that point to the plain
Kamelets.
Co-authored-by: Claude Opus 5.5 <[email protected]>
---
.../camel-kamelets-catalog-sbom.json | 2 +-
.../jms-apache-artemis-sink-description.adoc | 16 +++++++-
.../jms-apache-artemis-source-description.adoc | 12 +++---
...jms-pooled-apache-artemis-sink-description.adoc | 3 ++
...s-pooled-apache-artemis-source-description.adoc | 3 ++
kamelets/jms-amqp-10-sink.kamelet.yaml | 2 +-
kamelets/jms-amqp-10-source.kamelet.yaml | 2 +-
kamelets/jms-apache-artemis-sink.kamelet.yaml | 44 ++++++++++++++++++++--
kamelets/jms-apache-artemis-source.kamelet.yaml | 19 +++++++++-
.../jms-pooled-apache-artemis-sink.kamelet.yaml | 6 +--
.../jms-pooled-apache-artemis-source.kamelet.yaml | 6 +--
.../main/resources/META-INF/kamelets-index.json | 20 +++++-----
.../kamelets/jms-amqp-10-sink.kamelet.yaml | 2 +-
.../kamelets/jms-amqp-10-source.kamelet.yaml | 2 +-
.../kamelets/jms-apache-artemis-sink.kamelet.yaml | 44 ++++++++++++++++++++--
.../jms-apache-artemis-source.kamelet.yaml | 19 +++++++++-
.../jms-pooled-apache-artemis-sink.kamelet.yaml | 6 +--
.../jms-pooled-apache-artemis-source.kamelet.yaml | 6 +--
18 files changed, 171 insertions(+), 43 deletions(-)
diff --git a/camel-kamelets-sbom/camel-kamelets-catalog-sbom.json
b/camel-kamelets-sbom/camel-kamelets-catalog-sbom.json
index 58f1c7158..096b32681 100644
--- a/camel-kamelets-sbom/camel-kamelets-catalog-sbom.json
+++ b/camel-kamelets-sbom/camel-kamelets-catalog-sbom.json
@@ -2759,7 +2759,7 @@
"dependsOn" : [ "pkg:maven/org.apache.camel/[email protected]",
"pkg:maven/org.apache.camel/[email protected]",
"pkg:maven/org.apache.camel/[email protected]" ]
}, {
"ref" : "kamelet:jms-apache-artemis-sink",
- "dependsOn" : [
"pkg:maven/org.apache.activemq/[email protected]",
"pkg:maven/org.apache.camel/[email protected]",
"pkg:maven/org.apache.camel/[email protected]" ]
+ "dependsOn" : [
"pkg:maven/org.apache.activemq/[email protected]",
"pkg:maven/org.apache.camel/[email protected]",
"pkg:maven/org.apache.camel/[email protected]",
"pkg:maven/org.messaginghub/[email protected]" ]
}, {
"ref" : "kamelet:jms-apache-artemis-source",
"dependsOn" : [
"pkg:maven/org.apache.activemq/[email protected]",
"pkg:maven/org.apache.camel/[email protected]",
"pkg:maven/org.apache.camel/[email protected]" ]
diff --git
a/docs/modules/ROOT/partials/jms-apache-artemis-sink-description.adoc
b/docs/modules/ROOT/partials/jms-apache-artemis-sink-description.adoc
index 2c8c74183..717029ca9 100644
--- a/docs/modules/ROOT/partials/jms-apache-artemis-sink-description.adoc
+++ b/docs/modules/ROOT/partials/jms-apache-artemis-sink-description.adoc
@@ -10,4 +10,18 @@ The Kamelet supports both queue and topic destinations. The
destination type can
=== Apache Artemis Client
-This sink uses the Apache Artemis Jakarta JMS client library to establish
connections and send messages to the broker.
\ No newline at end of file
+This sink uses the Apache Artemis Jakarta JMS client library to establish
connections and send messages to the broker.
+
+=== Authentication
+
+A broker that needs a login takes it in the `username` and `password` options.
Without them, the Kamelet connects with
+no login.
+
+=== Connection Pooling
+
+The Kamelet keeps its connections to the broker in a pool and reuses them for
the next messages, instead of opening a
+new connection for each message. The pool is set with these options:
+
+- `maxSessionsPerConnection`: the most sessions open at the same time on each
connection (default: 500)
+- `maxIdleSessionsPerConnection`: how many unused sessions each connection
keeps for reuse (default: 500)
+- `connectionIdleTimeout`: how long an unused connection stays open, in
milliseconds (default: 30000)
diff --git
a/docs/modules/ROOT/partials/jms-apache-artemis-source-description.adoc
b/docs/modules/ROOT/partials/jms-apache-artemis-source-description.adoc
index 1d7a2bf01..6c873d33c 100644
--- a/docs/modules/ROOT/partials/jms-apache-artemis-source-description.adoc
+++ b/docs/modules/ROOT/partials/jms-apache-artemis-source-description.adoc
@@ -2,9 +2,8 @@
=== Authentication
-This Kamelet has no `username` and `password` options. A broker that needs a
login takes it in `brokerURL`, as
-`tcp://artemis.example.com:61616?user=artemisuser&password=artemispass`. To
keep the password in an option of its own,
-use `jms-pooled-apache-artemis-source`, which has `username` and `password`.
+A broker that needs a login takes it in the `username` and `password` options.
Without them, the Kamelet connects with
+no login.
=== Configuration
@@ -13,6 +12,7 @@ The JMS Apache Artemis Source Kamelet supports the following
configurations:
- **Broker URL**: Apache Artemis broker URL (required)
- **Destination Name**: JMS destination (queue or topic) name (required)
- **Destination Type**: Type of destination - queue or topic (default: queue)
+- **Username** and **Password**: the login to the broker, when it needs one
The subscription to a topic is not durable, and the Kamelet has no option for
a message selector.
@@ -47,7 +47,9 @@ The source receives only the messages published to the topic
while it is connect
from:
uri: "kamelet:jms-apache-artemis-source"
parameters:
- brokerURL:
"tcp://artemis.example.com:61616?user=artemisuser&password=artemispass"
+ brokerURL: "tcp://artemis.example.com:61616"
+ username: "artemisuser"
+ password: "artemispass"
destinationName: "events.topic"
destinationType: "topic"
steps:
@@ -58,4 +60,4 @@ The source receives only the messages published to the topic
while it is connect
=== Connection Management
When the broker cannot be reached, the Kamelet starts anyway and tries to
connect again every 5 seconds. It does not
-pool connections; `jms-pooled-apache-artemis-source` does.
+pool connections, and does not need to: it keeps its connection open while it
receives.
diff --git
a/docs/modules/ROOT/partials/jms-pooled-apache-artemis-sink-description.adoc
b/docs/modules/ROOT/partials/jms-pooled-apache-artemis-sink-description.adoc
index 6d9ff1042..8d7612605 100644
--- a/docs/modules/ROOT/partials/jms-pooled-apache-artemis-sink-description.adoc
+++ b/docs/modules/ROOT/partials/jms-pooled-apache-artemis-sink-description.adoc
@@ -1,5 +1,8 @@
== JMS Pooled - Apache Artemis Sink Kamelet Description
+NOTE: This Kamelet is deprecated and will be removed in a later release. Use
xref:jms-apache-artemis-sink.adoc[],
+which has the same options, including the pool, so only the name of the
Kamelet changes.
+
=== Connection Configuration
This Kamelet connects to an Apache Artemis message broker using JMS with
connection pooling for improved performance and resource management.
diff --git
a/docs/modules/ROOT/partials/jms-pooled-apache-artemis-source-description.adoc
b/docs/modules/ROOT/partials/jms-pooled-apache-artemis-source-description.adoc
index d2b0f1cc6..912deeec9 100644
---
a/docs/modules/ROOT/partials/jms-pooled-apache-artemis-source-description.adoc
+++
b/docs/modules/ROOT/partials/jms-pooled-apache-artemis-source-description.adoc
@@ -1,5 +1,8 @@
== JMS Pooled Apache Artemis Source Kamelet Description
+NOTE: This Kamelet is deprecated and will be removed in a later release. Use
xref:jms-apache-artemis-source.adoc[],
+which has the same `username` and `password` options. It needs no pool
options: a source keeps its connection open.
+
=== Authentication methods
This Kamelet connects to Apache Artemis JMS broker using:
diff --git a/kamelets/jms-amqp-10-sink.kamelet.yaml
b/kamelets/jms-amqp-10-sink.kamelet.yaml
index 88c92b9ed..2fa5027c0 100644
--- a/kamelets/jms-amqp-10-sink.kamelet.yaml
+++ b/kamelets/jms-amqp-10-sink.kamelet.yaml
@@ -34,7 +34,7 @@ spec:
description: |-
Sends each message to a queue or a topic in a message broker that speaks
AMQP 1.0, such as Apache ActiveMQ Artemis, through JMS and the Apache Qpid
client.
- Use it to hand work to another application through a queue, or to
publish events on a topic, on any broker that supports the AMQP 1.0 protocol.
For an Artemis broker, `jms-apache-artemis-sink` and
`jms-pooled-apache-artemis-sink` work too.
+ Use it to hand work to another application through a queue, or to
publish events on a topic, on any broker that supports the AMQP 1.0 protocol.
For an Artemis broker, `jms-apache-artemis-sink` works too.
Input: text is sent as a JMS text message, bytes as a JMS bytes message,
and a Map as a JMS map message. The headers of the message, except the Camel
ones, are sent along as JMS properties of the message.
diff --git a/kamelets/jms-amqp-10-source.kamelet.yaml
b/kamelets/jms-amqp-10-source.kamelet.yaml
index fe07533c6..dea317a71 100644
--- a/kamelets/jms-amqp-10-source.kamelet.yaml
+++ b/kamelets/jms-amqp-10-source.kamelet.yaml
@@ -34,7 +34,7 @@ spec:
description: |-
Receives each message from a queue or a topic in a message broker that
speaks AMQP 1.0, such as Apache ActiveMQ Artemis, through JMS and the Apache
Qpid client.
- Use it to process work that other applications put on a queue, or to
react to events published on a topic, on any broker that supports the AMQP 1.0
protocol. For an Artemis broker, `jms-apache-artemis-source` and
`jms-pooled-apache-artemis-source` work too.
+ Use it to process work that other applications put on a queue, or to
react to events published on a topic, on any broker that supports the AMQP 1.0
protocol. For an Artemis broker, `jms-apache-artemis-source` works too.
Output: the body is text for a JMS text message, bytes for a bytes
message, and a Map for a map message. The JMS properties of the message become
headers, along with the JMS headers such as `JMSMessageID`, `JMSDestination`,
`JMSTimestamp`, `JMSPriority` and `JMSRedelivered`.
diff --git a/kamelets/jms-apache-artemis-sink.kamelet.yaml
b/kamelets/jms-apache-artemis-sink.kamelet.yaml
index 8f51c3fda..3c2cd4e78 100644
--- a/kamelets/jms-apache-artemis-sink.kamelet.yaml
+++ b/kamelets/jms-apache-artemis-sink.kamelet.yaml
@@ -34,13 +34,13 @@ spec:
description: |-
Sends each message to a queue or a topic in an Apache ActiveMQ Artemis
broker, through JMS.
- Use it to hand work to another application through a queue, such as
orders to process, or to publish events on a topic for every application that
listens. For a steady flow of messages, use `jms-pooled-apache-artemis-sink`,
which reuses its connections to the broker and has `username` and `password`
options. For another broker that speaks AMQP 1.0, use `jms-amqp-10-sink`.
+ Use it to hand work to another application through a queue, such as
orders to process, or to publish events on a topic for every application that
listens. For another broker that speaks AMQP 1.0, use `jms-amqp-10-sink`.
Input: text is sent as a JMS text message, bytes as a JMS bytes message,
and a Map as a JMS map message. The headers of the message, except the Camel
ones, are sent along as JMS properties of the message.
Output: the message is unchanged.
- Good to know: Messages go to a queue unless `destinationType` is
`topic`, and a message sent to a topic reaches only the receivers subscribed at
that moment. It connects with no TLS and no login, unless `brokerURL` asks for
them. It does not wait for a reply, even when the incoming message expects one,
as one from `webhook-source` does.
+ Good to know: Messages go to a queue unless `destinationType` is
`topic`, and a message sent to a topic reaches only the receivers subscribed at
that moment. It connects with no TLS unless `brokerURL` asks for it, and logs
in with `username` and `password` when they are set. It keeps its connections
to the broker in a pool and reuses them for the next messages. It does not wait
for a reply, even when the incoming message expects one, as one from
`webhook-source` does.
required:
- destinationName
- brokerURL
@@ -61,16 +61,54 @@ spec:
description: "The address of the Artemis broker, as `tcp://host:port`;
the usual port is 61616. Add `?sslEnabled=true` for TLS. A broker that needs a
login takes it in the URL too, as `tcp://host:61616?user=app&password=secret`."
type: string
example: "tcp://localhost:61616"
+ username:
+ title: "Broker Username"
+ description: "The user name to log in to the broker with. Leave it
empty for a broker that accepts clients without a login."
+ type: string
+ x-descriptors:
+ - urn:camel:group:credentials
+ password:
+ title: "Broker Password"
+ description: "The password to log in to the broker with, for the user
`username`."
+ type: string
+ format: password
+ x-descriptors:
+ - urn:camel:group:credentials
+ maxSessionsPerConnection:
+ title: "Max Sessions Per Connection"
+ description: "The most sessions that can be open at the same time on
each connection of the pool. Each message being sent or received uses one
session."
+ type: integer
+ default: 500
+ maxIdleSessionsPerConnection:
+ title: "Max Idle Sessions Per Connection"
+ description: "How many unused sessions each connection of the pool
keeps open for reuse. Unused sessions beyond this number are closed."
+ type: integer
+ default: 500
+ connectionIdleTimeout:
+ title: "Connection Idle Timeout"
+ description: "How long a connection of the pool can stay unused before
it is closed, in milliseconds. For example, 30000 is 30 seconds."
+ type: integer
+ default: 30000
dependencies:
- "camel:jms"
- "camel:kamelet"
- "mvn:org.apache.activemq:artemis-jakarta-client-all:2.57.0"
+ - "mvn:org.messaginghub:pooled-jms:3.2.6"
template:
beans:
- name: connectionFactoryBean
type:
"#class:org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory"
properties:
brokerURL: "{{brokerURL}}"
+ user: "{{?username}}"
+ password: "{{?password}}"
+ - name: pooledFactoryBean
+ type: "#class:org.messaginghub.pooled.jms.JmsPoolConnectionFactory"
+ properties:
+ connectionFactory: "#bean:{{connectionFactoryBean}}"
+ maxSessionsPerConnection: "{{maxSessionsPerConnection}}"
+ maxIdleSessionsPerConnection: "{{maxIdleSessionsPerConnection}}"
+ connectionIdleTimeout: "{{connectionIdleTimeout}}"
from:
uri: kamelet:source
steps:
@@ -80,4 +118,4 @@ spec:
parameters:
destinationType: "{{destinationType}}"
destinationName: "{{destinationName}}"
- connectionFactory: "#bean:{{connectionFactoryBean}}"
+ connectionFactory: "#bean:{{pooledFactoryBean}}"
diff --git a/kamelets/jms-apache-artemis-source.kamelet.yaml
b/kamelets/jms-apache-artemis-source.kamelet.yaml
index e42e0034a..7bcbcc005 100644
--- a/kamelets/jms-apache-artemis-source.kamelet.yaml
+++ b/kamelets/jms-apache-artemis-source.kamelet.yaml
@@ -34,11 +34,11 @@ spec:
description: |-
Receives each message from a queue or a topic in an Apache ActiveMQ
Artemis broker, through JMS.
- Use it to process work that other applications put on a queue, such as
orders or jobs, or to react to events published on a topic.
`jms-pooled-apache-artemis-source` does the same with a pool of connections and
has `username` and `password` options. For another broker that speaks AMQP 1.0,
use `jms-amqp-10-source`.
+ Use it to process work that other applications put on a queue, such as
orders or jobs, or to react to events published on a topic. For another broker
that speaks AMQP 1.0, use `jms-amqp-10-source`.
Output: the body is text for a JMS text message, bytes for a bytes
message, and a Map for a map message. The JMS properties of the message become
headers, along with the JMS headers such as `JMSMessageID`, `JMSDestination`,
`JMSTimestamp`, `JMSPriority` and `JMSRedelivered`.
- Good to know: From a queue, each message is removed when it is received,
even when the rest of the flow then fails, and several copies of this source
share the messages. From a topic (`destinationType` set to `topic`), it
receives only the messages sent while it is connected, as the subscription is
not durable. It connects with no TLS and no login, unless `brokerURL` asks for
them. When the broker cannot be reached, it starts anyway and tries again every
5 seconds.
+ Good to know: From a queue, each message is removed when it is received,
even when the rest of the flow then fails, and several copies of this source
share the messages. From a topic (`destinationType` set to `topic`), it
receives only the messages sent while it is connected, as the subscription is
not durable. It connects with no TLS unless `brokerURL` asks for it, and logs
in with `username` and `password` when they are set. When the broker cannot be
reached, it starts anyway and [...]
required:
- destinationName
- brokerURL
@@ -59,6 +59,19 @@ spec:
description: "The address of the Artemis broker, as `tcp://host:port`;
the usual port is 61616. Add `?sslEnabled=true` for TLS. A broker that needs a
login takes it in the URL too, as `tcp://host:61616?user=app&password=secret`."
type: string
example: "tcp://localhost:61616"
+ username:
+ title: "Broker Username"
+ description: "The user name to log in to the broker with. Leave it
empty for a broker that accepts clients without a login."
+ type: string
+ x-descriptors:
+ - urn:camel:group:credentials
+ password:
+ title: "Broker Password"
+ description: "The password to log in to the broker with, for the user
`username`."
+ type: string
+ format: password
+ x-descriptors:
+ - urn:camel:group:credentials
dataTypes:
out:
headers:
@@ -88,6 +101,8 @@ spec:
type:
"#class:org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory"
properties:
brokerURL: "{{brokerURL}}"
+ user: "{{?username}}"
+ password: "{{?password}}"
from:
uri: jms
parameters:
diff --git a/kamelets/jms-pooled-apache-artemis-sink.kamelet.yaml
b/kamelets/jms-pooled-apache-artemis-sink.kamelet.yaml
index a1982c6bc..ed3348953 100644
--- a/kamelets/jms-pooled-apache-artemis-sink.kamelet.yaml
+++ b/kamelets/jms-pooled-apache-artemis-sink.kamelet.yaml
@@ -20,7 +20,7 @@ metadata:
name: jms-pooled-apache-artemis-sink
annotations:
camel.apache.org/kamelet.icon:
"data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiIHN0YW5kYWxvbmU9Im5vIj8+CjwhLS0gQ3JlYXRlZCB3aXRoIElua3NjYXBlIChodHRwOi8vd3d3Lmlua3NjYXBlLm9yZy8pIC0tPgoKPHN2ZwogICB4bWxuczpkYz0iaHR0cDovL3B1cmwub3JnL2RjL2VsZW1lbnRzLzEuMS8iCiAgIHhtbG5zOmNjPSJodHRwOi8vY3JlYXRpdmVjb21tb25zLm9yZy9ucyMiCiAgIHhtbG5zOnJkZj0iaHR0cDovL3d3dy53My5vcmcvMTk5OS8wMi8yMi1yZGYtc3ludGF4LW5zIyIKICAgeG1sbnM6c3ZnPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIKICAgeG1sbnM9Im
[...]
- camel.apache.org/kamelet.support.level: "Stable"
+ camel.apache.org/kamelet.support.level: "Deprecated"
camel.apache.org/provider: "Apache Software Foundation"
camel.apache.org/catalog.version: "4.24.0-SNAPSHOT"
camel.apache.org/kamelet.group: "JMS"
@@ -32,9 +32,9 @@ spec:
definition:
title: "JMS Pooled - Apache Artemis Sink"
description: |-
- Sends each message to a queue or a topic in an Apache ActiveMQ Artemis
broker, through JMS, reusing a pool of connections to the broker.
+ Deprecated, use `jms-apache-artemis-sink` instead, which now has the
same options: sends each message to a queue or a topic in an Apache ActiveMQ
Artemis broker.
- Use it to hand work to another application through a queue, or to
publish events on a topic, when messages flow steadily: it reuses its
connections, where `jms-apache-artemis-sink` connects anew for each message.
Use it also for a broker that needs a login, which goes in `username` and
`password`.
+ Use it to hand work to another application through a queue, or to
publish events on a topic, when messages flow steadily: it reuses its
connections, where `jms-apache-artemis-sink` connects anew for each message.
This Kamelet will be removed in a later release: `jms-apache-artemis-sink` now
takes the same options and reuses its connections too, so change only the name
of the Kamelet.
Input: text is sent as a JMS text message, bytes as a JMS bytes message,
and a Map as a JMS map message. The headers of the message, except the Camel
ones, are sent along as JMS properties of the message.
diff --git a/kamelets/jms-pooled-apache-artemis-source.kamelet.yaml
b/kamelets/jms-pooled-apache-artemis-source.kamelet.yaml
index 20448cea0..6a82142c3 100644
--- a/kamelets/jms-pooled-apache-artemis-source.kamelet.yaml
+++ b/kamelets/jms-pooled-apache-artemis-source.kamelet.yaml
@@ -20,7 +20,7 @@ metadata:
name: jms-pooled-apache-artemis-source
annotations:
camel.apache.org/kamelet.icon:
"data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiIHN0YW5kYWxvbmU9Im5vIj8+CjwhLS0gQ3JlYXRlZCB3aXRoIElua3NjYXBlIChodHRwOi8vd3d3Lmlua3NjYXBlLm9yZy8pIC0tPgoKPHN2ZwogICB4bWxuczpkYz0iaHR0cDovL3B1cmwub3JnL2RjL2VsZW1lbnRzLzEuMS8iCiAgIHhtbG5zOmNjPSJodHRwOi8vY3JlYXRpdmVjb21tb25zLm9yZy9ucyMiCiAgIHhtbG5zOnJkZj0iaHR0cDovL3d3dy53My5vcmcvMTk5OS8wMi8yMi1yZGYtc3ludGF4LW5zIyIKICAgeG1sbnM6c3ZnPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIKICAgeG1sbnM9Im
[...]
- camel.apache.org/kamelet.support.level: "Stable"
+ camel.apache.org/kamelet.support.level: "Deprecated"
camel.apache.org/provider: "Apache Software Foundation"
camel.apache.org/catalog.version: "4.24.0-SNAPSHOT"
camel.apache.org/kamelet.group: "JMS"
@@ -32,9 +32,9 @@ spec:
definition:
title: "JMS Pooled - Apache Artemis Source"
description: |-
- Receives each message from a queue or a topic in an Apache ActiveMQ
Artemis broker, through JMS, with connections taken from a pool.
+ Deprecated, use `jms-apache-artemis-source` instead, which now has the
same login options: receives each message from a queue or a topic in an Apache
ActiveMQ Artemis broker.
- Use it to process work that other applications put on a queue, or to
react to events published on a topic, on a broker that needs a login: it is
`jms-apache-artemis-source` with `username` and `password` options and a pool
of connections.
+ Use it to process work that other applications put on a queue, or to
react to events published on a topic, on a broker that needs a login. This
Kamelet will be removed in a later release: `jms-apache-artemis-source` now
takes `username` and `password`, so change the name of the Kamelet and drop the
pool options, which a source does not need because it keeps its connection open.
Output: the body is text for a JMS text message, bytes for a bytes
message, and a Map for a map message. The JMS properties of the message become
headers, along with the JMS headers such as `JMSMessageID`, `JMSDestination`,
`JMSTimestamp`, `JMSPriority` and `JMSRedelivered`.
diff --git
a/library/camel-kamelets/src/main/resources/META-INF/kamelets-index.json
b/library/camel-kamelets/src/main/resources/META-INF/kamelets-index.json
index 775edce4a..dd0f7af7e 100644
--- a/library/camel-kamelets/src/main/resources/META-INF/kamelets-index.json
+++ b/library/camel-kamelets/src/main/resources/META-INF/kamelets-index.json
@@ -1205,7 +1205,7 @@
"supportLevel" : "Stable",
"title" : "JMS - AMQP 1.0 Sink",
"summary" : "Sends each message to a queue or a topic in a message broker
that speaks AMQP 1.0, such as Apache ActiveMQ Artemis, through JMS and the
Apache Qpid client.",
- "description" : "Sends each message to a queue or a topic in a message
broker that speaks AMQP 1.0, such as Apache ActiveMQ Artemis, through JMS and
the Apache Qpid client.\n\nUse it to hand work to another application through a
queue, or to publish events on a topic, on any broker that supports the AMQP
1.0 protocol. For an Artemis broker, `jms-apache-artemis-sink` and
`jms-pooled-apache-artemis-sink` work too.\n\nInput: text is sent as a JMS text
message, bytes as a JMS bytes messa [...]
+ "description" : "Sends each message to a queue or a topic in a message
broker that speaks AMQP 1.0, such as Apache ActiveMQ Artemis, through JMS and
the Apache Qpid client.\n\nUse it to hand work to another application through a
queue, or to publish events on a topic, on any broker that supports the AMQP
1.0 protocol. For an Artemis broker, `jms-apache-artemis-sink` works
too.\n\nInput: text is sent as a JMS text message, bytes as a JMS bytes
message, and a Map as a JMS map message. [...]
"group" : "JMS",
"namespace" : "Messaging",
"provider" : "Apache Software Foundation"
@@ -1215,7 +1215,7 @@
"supportLevel" : "Stable",
"title" : "JMS - AMQP 1.0 Source",
"summary" : "Receives each message from a queue or a topic in a message
broker that speaks AMQP 1.0, such as Apache ActiveMQ Artemis, through JMS and
the Apache Qpid client.",
- "description" : "Receives each message from a queue or a topic in a
message broker that speaks AMQP 1.0, such as Apache ActiveMQ Artemis, through
JMS and the Apache Qpid client.\n\nUse it to process work that other
applications put on a queue, or to react to events published on a topic, on any
broker that supports the AMQP 1.0 protocol. For an Artemis broker,
`jms-apache-artemis-source` and `jms-pooled-apache-artemis-source` work
too.\n\nOutput: the body is text for a JMS text messag [...]
+ "description" : "Receives each message from a queue or a topic in a
message broker that speaks AMQP 1.0, such as Apache ActiveMQ Artemis, through
JMS and the Apache Qpid client.\n\nUse it to process work that other
applications put on a queue, or to react to events published on a topic, on any
broker that supports the AMQP 1.0 protocol. For an Artemis broker,
`jms-apache-artemis-source` works too.\n\nOutput: the body is text for a JMS
text message, bytes for a bytes message, and a Ma [...]
"group" : "JMS",
"namespace" : "Messaging",
"provider" : "Apache Software Foundation"
@@ -1225,7 +1225,7 @@
"supportLevel" : "Stable",
"title" : "JMS - Apache Artemis Sink",
"summary" : "Sends each message to a queue or a topic in an Apache
ActiveMQ Artemis broker, through JMS.",
- "description" : "Sends each message to a queue or a topic in an Apache
ActiveMQ Artemis broker, through JMS.\n\nUse it to hand work to another
application through a queue, such as orders to process, or to publish events on
a topic for every application that listens. For a steady flow of messages, use
`jms-pooled-apache-artemis-sink`, which reuses its connections to the broker
and has `username` and `password` options. For another broker that speaks AMQP
1.0, use `jms-amqp-10-sink`.\n [...]
+ "description" : "Sends each message to a queue or a topic in an Apache
ActiveMQ Artemis broker, through JMS.\n\nUse it to hand work to another
application through a queue, such as orders to process, or to publish events on
a topic for every application that listens. For another broker that speaks AMQP
1.0, use `jms-amqp-10-sink`.\n\nInput: text is sent as a JMS text message,
bytes as a JMS bytes message, and a Map as a JMS map message. The headers of
the message, except the Camel one [...]
"group" : "JMS",
"namespace" : "Messaging",
"provider" : "Apache Software Foundation"
@@ -1235,7 +1235,7 @@
"supportLevel" : "Stable",
"title" : "JMS - Apache Artemis Source",
"summary" : "Receives each message from a queue or a topic in an Apache
ActiveMQ Artemis broker, through JMS.",
- "description" : "Receives each message from a queue or a topic in an
Apache ActiveMQ Artemis broker, through JMS.\n\nUse it to process work that
other applications put on a queue, such as orders or jobs, or to react to
events published on a topic. `jms-pooled-apache-artemis-source` does the same
with a pool of connections and has `username` and `password` options. For
another broker that speaks AMQP 1.0, use `jms-amqp-10-source`.\n\nOutput: the
body is text for a JMS text message, by [...]
+ "description" : "Receives each message from a queue or a topic in an
Apache ActiveMQ Artemis broker, through JMS.\n\nUse it to process work that
other applications put on a queue, such as orders or jobs, or to react to
events published on a topic. For another broker that speaks AMQP 1.0, use
`jms-amqp-10-source`.\n\nOutput: the body is text for a JMS text message, bytes
for a bytes message, and a Map for a map message. The JMS properties of the
message become headers, along with the [...]
"group" : "JMS",
"namespace" : "Messaging",
"provider" : "Apache Software Foundation"
@@ -1262,20 +1262,20 @@
}, {
"name" : "jms-pooled-apache-artemis-sink",
"type" : "sink",
- "supportLevel" : "Stable",
+ "supportLevel" : "Deprecated",
"title" : "JMS Pooled - Apache Artemis Sink",
- "summary" : "Sends each message to a queue or a topic in an Apache
ActiveMQ Artemis broker, through JMS, reusing a pool of connections to the
broker.",
- "description" : "Sends each message to a queue or a topic in an Apache
ActiveMQ Artemis broker, through JMS, reusing a pool of connections to the
broker.\n\nUse it to hand work to another application through a queue, or to
publish events on a topic, when messages flow steadily: it reuses its
connections, where `jms-apache-artemis-sink` connects anew for each message.
Use it also for a broker that needs a login, which goes in `username` and
`password`.\n\nInput: text is sent as a JMS [...]
+ "summary" : "Deprecated, use `jms-apache-artemis-sink` instead, which now
has the same options: sends each message to a queue or a topic in an Apache
ActiveMQ Artemis broker.",
+ "description" : "Deprecated, use `jms-apache-artemis-sink` instead, which
now has the same options: sends each message to a queue or a topic in an Apache
ActiveMQ Artemis broker.\n\nUse it to hand work to another application through
a queue, or to publish events on a topic, when messages flow steadily: it
reuses its connections, where `jms-apache-artemis-sink` connects anew for each
message. This Kamelet will be removed in a later release:
`jms-apache-artemis-sink` now takes the same [...]
"group" : "JMS",
"namespace" : "Messaging",
"provider" : "Apache Software Foundation"
}, {
"name" : "jms-pooled-apache-artemis-source",
"type" : "source",
- "supportLevel" : "Stable",
+ "supportLevel" : "Deprecated",
"title" : "JMS Pooled - Apache Artemis Source",
- "summary" : "Receives each message from a queue or a topic in an Apache
ActiveMQ Artemis broker, through JMS, with connections taken from a pool.",
- "description" : "Receives each message from a queue or a topic in an
Apache ActiveMQ Artemis broker, through JMS, with connections taken from a
pool.\n\nUse it to process work that other applications put on a queue, or to
react to events published on a topic, on a broker that needs a login: it is
`jms-apache-artemis-source` with `username` and `password` options and a pool
of connections.\n\nOutput: the body is text for a JMS text message, bytes for a
bytes message, and a Map for a m [...]
+ "summary" : "Deprecated, use `jms-apache-artemis-source` instead, which
now has the same login options: receives each message from a queue or a topic
in an Apache ActiveMQ Artemis broker.",
+ "description" : "Deprecated, use `jms-apache-artemis-source` instead,
which now has the same login options: receives each message from a queue or a
topic in an Apache ActiveMQ Artemis broker.\n\nUse it to process work that
other applications put on a queue, or to react to events published on a topic,
on a broker that needs a login. This Kamelet will be removed in a later
release: `jms-apache-artemis-source` now takes `username` and `password`, so
change the name of the Kamelet and dr [...]
"group" : "JMS",
"namespace" : "Messaging",
"provider" : "Apache Software Foundation"
diff --git
a/library/camel-kamelets/src/main/resources/kamelets/jms-amqp-10-sink.kamelet.yaml
b/library/camel-kamelets/src/main/resources/kamelets/jms-amqp-10-sink.kamelet.yaml
index 88c92b9ed..2fa5027c0 100644
---
a/library/camel-kamelets/src/main/resources/kamelets/jms-amqp-10-sink.kamelet.yaml
+++
b/library/camel-kamelets/src/main/resources/kamelets/jms-amqp-10-sink.kamelet.yaml
@@ -34,7 +34,7 @@ spec:
description: |-
Sends each message to a queue or a topic in a message broker that speaks
AMQP 1.0, such as Apache ActiveMQ Artemis, through JMS and the Apache Qpid
client.
- Use it to hand work to another application through a queue, or to
publish events on a topic, on any broker that supports the AMQP 1.0 protocol.
For an Artemis broker, `jms-apache-artemis-sink` and
`jms-pooled-apache-artemis-sink` work too.
+ Use it to hand work to another application through a queue, or to
publish events on a topic, on any broker that supports the AMQP 1.0 protocol.
For an Artemis broker, `jms-apache-artemis-sink` works too.
Input: text is sent as a JMS text message, bytes as a JMS bytes message,
and a Map as a JMS map message. The headers of the message, except the Camel
ones, are sent along as JMS properties of the message.
diff --git
a/library/camel-kamelets/src/main/resources/kamelets/jms-amqp-10-source.kamelet.yaml
b/library/camel-kamelets/src/main/resources/kamelets/jms-amqp-10-source.kamelet.yaml
index fe07533c6..dea317a71 100644
---
a/library/camel-kamelets/src/main/resources/kamelets/jms-amqp-10-source.kamelet.yaml
+++
b/library/camel-kamelets/src/main/resources/kamelets/jms-amqp-10-source.kamelet.yaml
@@ -34,7 +34,7 @@ spec:
description: |-
Receives each message from a queue or a topic in a message broker that
speaks AMQP 1.0, such as Apache ActiveMQ Artemis, through JMS and the Apache
Qpid client.
- Use it to process work that other applications put on a queue, or to
react to events published on a topic, on any broker that supports the AMQP 1.0
protocol. For an Artemis broker, `jms-apache-artemis-source` and
`jms-pooled-apache-artemis-source` work too.
+ Use it to process work that other applications put on a queue, or to
react to events published on a topic, on any broker that supports the AMQP 1.0
protocol. For an Artemis broker, `jms-apache-artemis-source` works too.
Output: the body is text for a JMS text message, bytes for a bytes
message, and a Map for a map message. The JMS properties of the message become
headers, along with the JMS headers such as `JMSMessageID`, `JMSDestination`,
`JMSTimestamp`, `JMSPriority` and `JMSRedelivered`.
diff --git
a/library/camel-kamelets/src/main/resources/kamelets/jms-apache-artemis-sink.kamelet.yaml
b/library/camel-kamelets/src/main/resources/kamelets/jms-apache-artemis-sink.kamelet.yaml
index 8f51c3fda..3c2cd4e78 100644
---
a/library/camel-kamelets/src/main/resources/kamelets/jms-apache-artemis-sink.kamelet.yaml
+++
b/library/camel-kamelets/src/main/resources/kamelets/jms-apache-artemis-sink.kamelet.yaml
@@ -34,13 +34,13 @@ spec:
description: |-
Sends each message to a queue or a topic in an Apache ActiveMQ Artemis
broker, through JMS.
- Use it to hand work to another application through a queue, such as
orders to process, or to publish events on a topic for every application that
listens. For a steady flow of messages, use `jms-pooled-apache-artemis-sink`,
which reuses its connections to the broker and has `username` and `password`
options. For another broker that speaks AMQP 1.0, use `jms-amqp-10-sink`.
+ Use it to hand work to another application through a queue, such as
orders to process, or to publish events on a topic for every application that
listens. For another broker that speaks AMQP 1.0, use `jms-amqp-10-sink`.
Input: text is sent as a JMS text message, bytes as a JMS bytes message,
and a Map as a JMS map message. The headers of the message, except the Camel
ones, are sent along as JMS properties of the message.
Output: the message is unchanged.
- Good to know: Messages go to a queue unless `destinationType` is
`topic`, and a message sent to a topic reaches only the receivers subscribed at
that moment. It connects with no TLS and no login, unless `brokerURL` asks for
them. It does not wait for a reply, even when the incoming message expects one,
as one from `webhook-source` does.
+ Good to know: Messages go to a queue unless `destinationType` is
`topic`, and a message sent to a topic reaches only the receivers subscribed at
that moment. It connects with no TLS unless `brokerURL` asks for it, and logs
in with `username` and `password` when they are set. It keeps its connections
to the broker in a pool and reuses them for the next messages. It does not wait
for a reply, even when the incoming message expects one, as one from
`webhook-source` does.
required:
- destinationName
- brokerURL
@@ -61,16 +61,54 @@ spec:
description: "The address of the Artemis broker, as `tcp://host:port`;
the usual port is 61616. Add `?sslEnabled=true` for TLS. A broker that needs a
login takes it in the URL too, as `tcp://host:61616?user=app&password=secret`."
type: string
example: "tcp://localhost:61616"
+ username:
+ title: "Broker Username"
+ description: "The user name to log in to the broker with. Leave it
empty for a broker that accepts clients without a login."
+ type: string
+ x-descriptors:
+ - urn:camel:group:credentials
+ password:
+ title: "Broker Password"
+ description: "The password to log in to the broker with, for the user
`username`."
+ type: string
+ format: password
+ x-descriptors:
+ - urn:camel:group:credentials
+ maxSessionsPerConnection:
+ title: "Max Sessions Per Connection"
+ description: "The most sessions that can be open at the same time on
each connection of the pool. Each message being sent or received uses one
session."
+ type: integer
+ default: 500
+ maxIdleSessionsPerConnection:
+ title: "Max Idle Sessions Per Connection"
+ description: "How many unused sessions each connection of the pool
keeps open for reuse. Unused sessions beyond this number are closed."
+ type: integer
+ default: 500
+ connectionIdleTimeout:
+ title: "Connection Idle Timeout"
+ description: "How long a connection of the pool can stay unused before
it is closed, in milliseconds. For example, 30000 is 30 seconds."
+ type: integer
+ default: 30000
dependencies:
- "camel:jms"
- "camel:kamelet"
- "mvn:org.apache.activemq:artemis-jakarta-client-all:2.57.0"
+ - "mvn:org.messaginghub:pooled-jms:3.2.6"
template:
beans:
- name: connectionFactoryBean
type:
"#class:org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory"
properties:
brokerURL: "{{brokerURL}}"
+ user: "{{?username}}"
+ password: "{{?password}}"
+ - name: pooledFactoryBean
+ type: "#class:org.messaginghub.pooled.jms.JmsPoolConnectionFactory"
+ properties:
+ connectionFactory: "#bean:{{connectionFactoryBean}}"
+ maxSessionsPerConnection: "{{maxSessionsPerConnection}}"
+ maxIdleSessionsPerConnection: "{{maxIdleSessionsPerConnection}}"
+ connectionIdleTimeout: "{{connectionIdleTimeout}}"
from:
uri: kamelet:source
steps:
@@ -80,4 +118,4 @@ spec:
parameters:
destinationType: "{{destinationType}}"
destinationName: "{{destinationName}}"
- connectionFactory: "#bean:{{connectionFactoryBean}}"
+ connectionFactory: "#bean:{{pooledFactoryBean}}"
diff --git
a/library/camel-kamelets/src/main/resources/kamelets/jms-apache-artemis-source.kamelet.yaml
b/library/camel-kamelets/src/main/resources/kamelets/jms-apache-artemis-source.kamelet.yaml
index e42e0034a..7bcbcc005 100644
---
a/library/camel-kamelets/src/main/resources/kamelets/jms-apache-artemis-source.kamelet.yaml
+++
b/library/camel-kamelets/src/main/resources/kamelets/jms-apache-artemis-source.kamelet.yaml
@@ -34,11 +34,11 @@ spec:
description: |-
Receives each message from a queue or a topic in an Apache ActiveMQ
Artemis broker, through JMS.
- Use it to process work that other applications put on a queue, such as
orders or jobs, or to react to events published on a topic.
`jms-pooled-apache-artemis-source` does the same with a pool of connections and
has `username` and `password` options. For another broker that speaks AMQP 1.0,
use `jms-amqp-10-source`.
+ Use it to process work that other applications put on a queue, such as
orders or jobs, or to react to events published on a topic. For another broker
that speaks AMQP 1.0, use `jms-amqp-10-source`.
Output: the body is text for a JMS text message, bytes for a bytes
message, and a Map for a map message. The JMS properties of the message become
headers, along with the JMS headers such as `JMSMessageID`, `JMSDestination`,
`JMSTimestamp`, `JMSPriority` and `JMSRedelivered`.
- Good to know: From a queue, each message is removed when it is received,
even when the rest of the flow then fails, and several copies of this source
share the messages. From a topic (`destinationType` set to `topic`), it
receives only the messages sent while it is connected, as the subscription is
not durable. It connects with no TLS and no login, unless `brokerURL` asks for
them. When the broker cannot be reached, it starts anyway and tries again every
5 seconds.
+ Good to know: From a queue, each message is removed when it is received,
even when the rest of the flow then fails, and several copies of this source
share the messages. From a topic (`destinationType` set to `topic`), it
receives only the messages sent while it is connected, as the subscription is
not durable. It connects with no TLS unless `brokerURL` asks for it, and logs
in with `username` and `password` when they are set. When the broker cannot be
reached, it starts anyway and [...]
required:
- destinationName
- brokerURL
@@ -59,6 +59,19 @@ spec:
description: "The address of the Artemis broker, as `tcp://host:port`;
the usual port is 61616. Add `?sslEnabled=true` for TLS. A broker that needs a
login takes it in the URL too, as `tcp://host:61616?user=app&password=secret`."
type: string
example: "tcp://localhost:61616"
+ username:
+ title: "Broker Username"
+ description: "The user name to log in to the broker with. Leave it
empty for a broker that accepts clients without a login."
+ type: string
+ x-descriptors:
+ - urn:camel:group:credentials
+ password:
+ title: "Broker Password"
+ description: "The password to log in to the broker with, for the user
`username`."
+ type: string
+ format: password
+ x-descriptors:
+ - urn:camel:group:credentials
dataTypes:
out:
headers:
@@ -88,6 +101,8 @@ spec:
type:
"#class:org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory"
properties:
brokerURL: "{{brokerURL}}"
+ user: "{{?username}}"
+ password: "{{?password}}"
from:
uri: jms
parameters:
diff --git
a/library/camel-kamelets/src/main/resources/kamelets/jms-pooled-apache-artemis-sink.kamelet.yaml
b/library/camel-kamelets/src/main/resources/kamelets/jms-pooled-apache-artemis-sink.kamelet.yaml
index a1982c6bc..ed3348953 100644
---
a/library/camel-kamelets/src/main/resources/kamelets/jms-pooled-apache-artemis-sink.kamelet.yaml
+++
b/library/camel-kamelets/src/main/resources/kamelets/jms-pooled-apache-artemis-sink.kamelet.yaml
@@ -20,7 +20,7 @@ metadata:
name: jms-pooled-apache-artemis-sink
annotations:
camel.apache.org/kamelet.icon:
"data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiIHN0YW5kYWxvbmU9Im5vIj8+CjwhLS0gQ3JlYXRlZCB3aXRoIElua3NjYXBlIChodHRwOi8vd3d3Lmlua3NjYXBlLm9yZy8pIC0tPgoKPHN2ZwogICB4bWxuczpkYz0iaHR0cDovL3B1cmwub3JnL2RjL2VsZW1lbnRzLzEuMS8iCiAgIHhtbG5zOmNjPSJodHRwOi8vY3JlYXRpdmVjb21tb25zLm9yZy9ucyMiCiAgIHhtbG5zOnJkZj0iaHR0cDovL3d3dy53My5vcmcvMTk5OS8wMi8yMi1yZGYtc3ludGF4LW5zIyIKICAgeG1sbnM6c3ZnPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIKICAgeG1sbnM9Im
[...]
- camel.apache.org/kamelet.support.level: "Stable"
+ camel.apache.org/kamelet.support.level: "Deprecated"
camel.apache.org/provider: "Apache Software Foundation"
camel.apache.org/catalog.version: "4.24.0-SNAPSHOT"
camel.apache.org/kamelet.group: "JMS"
@@ -32,9 +32,9 @@ spec:
definition:
title: "JMS Pooled - Apache Artemis Sink"
description: |-
- Sends each message to a queue or a topic in an Apache ActiveMQ Artemis
broker, through JMS, reusing a pool of connections to the broker.
+ Deprecated, use `jms-apache-artemis-sink` instead, which now has the
same options: sends each message to a queue or a topic in an Apache ActiveMQ
Artemis broker.
- Use it to hand work to another application through a queue, or to
publish events on a topic, when messages flow steadily: it reuses its
connections, where `jms-apache-artemis-sink` connects anew for each message.
Use it also for a broker that needs a login, which goes in `username` and
`password`.
+ Use it to hand work to another application through a queue, or to
publish events on a topic, when messages flow steadily: it reuses its
connections, where `jms-apache-artemis-sink` connects anew for each message.
This Kamelet will be removed in a later release: `jms-apache-artemis-sink` now
takes the same options and reuses its connections too, so change only the name
of the Kamelet.
Input: text is sent as a JMS text message, bytes as a JMS bytes message,
and a Map as a JMS map message. The headers of the message, except the Camel
ones, are sent along as JMS properties of the message.
diff --git
a/library/camel-kamelets/src/main/resources/kamelets/jms-pooled-apache-artemis-source.kamelet.yaml
b/library/camel-kamelets/src/main/resources/kamelets/jms-pooled-apache-artemis-source.kamelet.yaml
index 20448cea0..6a82142c3 100644
---
a/library/camel-kamelets/src/main/resources/kamelets/jms-pooled-apache-artemis-source.kamelet.yaml
+++
b/library/camel-kamelets/src/main/resources/kamelets/jms-pooled-apache-artemis-source.kamelet.yaml
@@ -20,7 +20,7 @@ metadata:
name: jms-pooled-apache-artemis-source
annotations:
camel.apache.org/kamelet.icon:
"data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiIHN0YW5kYWxvbmU9Im5vIj8+CjwhLS0gQ3JlYXRlZCB3aXRoIElua3NjYXBlIChodHRwOi8vd3d3Lmlua3NjYXBlLm9yZy8pIC0tPgoKPHN2ZwogICB4bWxuczpkYz0iaHR0cDovL3B1cmwub3JnL2RjL2VsZW1lbnRzLzEuMS8iCiAgIHhtbG5zOmNjPSJodHRwOi8vY3JlYXRpdmVjb21tb25zLm9yZy9ucyMiCiAgIHhtbG5zOnJkZj0iaHR0cDovL3d3dy53My5vcmcvMTk5OS8wMi8yMi1yZGYtc3ludGF4LW5zIyIKICAgeG1sbnM6c3ZnPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIKICAgeG1sbnM9Im
[...]
- camel.apache.org/kamelet.support.level: "Stable"
+ camel.apache.org/kamelet.support.level: "Deprecated"
camel.apache.org/provider: "Apache Software Foundation"
camel.apache.org/catalog.version: "4.24.0-SNAPSHOT"
camel.apache.org/kamelet.group: "JMS"
@@ -32,9 +32,9 @@ spec:
definition:
title: "JMS Pooled - Apache Artemis Source"
description: |-
- Receives each message from a queue or a topic in an Apache ActiveMQ
Artemis broker, through JMS, with connections taken from a pool.
+ Deprecated, use `jms-apache-artemis-source` instead, which now has the
same login options: receives each message from a queue or a topic in an Apache
ActiveMQ Artemis broker.
- Use it to process work that other applications put on a queue, or to
react to events published on a topic, on a broker that needs a login: it is
`jms-apache-artemis-source` with `username` and `password` options and a pool
of connections.
+ Use it to process work that other applications put on a queue, or to
react to events published on a topic, on a broker that needs a login. This
Kamelet will be removed in a later release: `jms-apache-artemis-source` now
takes `username` and `password`, so change the name of the Kamelet and drop the
pool options, which a source does not need because it keeps its connection open.
Output: the body is text for a JMS text message, bytes for a bytes
message, and a Map for a map message. The JMS properties of the message become
headers, along with the JMS headers such as `JMSMessageID`, `JMSDestination`,
`JMSTimestamp`, `JMSPriority` and `JMSRedelivered`.