Red Hat Summit Red Hat SummitSupportConsoleDéveloppeursCommencer un essaiContact

Ce contenu n'est pas disponible dans la langue sélectionnée.

6.2. Publish-Subscribe Channel

Overview
Copier lien

A publish-subscribe channel, shown in Figure 6.2, “Publish Subscribe Channel Pattern”, is a message channel that enables multiple subscribers to consume any given message. This is in contrast with a point-to-point channel. Publish-subscribe channels are frequently used as a means of broadcasting events or notifications to multiple subscribers.

Figure 6.2. Publish Subscribe Channel Pattern

Publish subscribe channel pattern
View larger image
Publish subscribe channel pattern

Components that support publish-subscribe channel
Copier lien

The following Apache Camel components support the publish-subscribe channel pattern:
  • JMS
  • ActiveMQ
  • XMPP
  • SEDA for working with SEDA in the same CamelContext which can work in pub-sub, but allowing multiple consumers.
  • VM as SEDA, but for use within the same JVM.

JMS
Copier lien

In JMS, a publish-subscribe channel is represented by a topic. For example, you can specify the endpoint URI for a JMS topic called StockQuotes as follows: 
jms:topic:StockQuotes
Copy to Clipboard Toggle word wrap
See chapter "JMS" in "Apache Camel Component Reference" for more details.

ActiveMQ
Copier lien

In ActiveMQ, a publish-subscribe channel is represented by a topic. For example, you can specify the endpoint URI for an ActiveMQ topic called StockQuotes, as follows: 
activemq:topic:StockQuotes
Copy to Clipboard Toggle word wrap
See chapter "ActiveMQ" in "Apache Camel Component Reference" for more details.

XMPP
Copier lien

The XMPP (Jabber) component supports the publish-subscribe channel pattern when it is used in the group communication mode. See chapter "XMPP" in "Apache Camel Component Reference" for more details.

Static subscription lists
Copier lien

If you prefer, you can also implement publish-subscribe logic within the Apache Camel application itself. A simple approach is to define a static subscription list, where the target endpoints are all explicitly listed at the end of the route. However, this approach is not as flexible as a JMS or ActiveMQ topic.

Java DSL example
Copier lien

The following Java DSL example shows how to simulate a publish-subscribe channel with a single publisher, seda:a, and three subscribers, seda:b, seda:c, and seda:d: 
from("seda:a").to("seda:b", "seda:c", "seda:d");
Copy to Clipboard Toggle word wrap
Note
This only works for the InOnly message exchange pattern.

XML configuration example
Copier lien

The following example shows how to configure the same route in XML: 
<camelContext id="buildStaticRecipientList" xmlns="http://camel.apache.org/schema/spring">
  <route>
    <from uri="seda:a"/>
    <to uri="seda:b"/>
    <to uri="seda:c"/>
    <to uri="seda:d"/>
  </route>
</camelContext>
Copy to Clipboard Toggle word wrap
Retour au début
Red Hat logoGithubredditYoutubeTwitter

Apprendre

Essayez, achetez et vendez

Communautés

À propos de la documentation Red Hat

Nous aidons les utilisateurs de Red Hat à innover et à atteindre leurs objectifs grâce à nos produits et services avec un contenu auquel ils peuvent faire confiance. Découvrez nos récentes mises à jour.

Rendre l’open source plus inclusif

Red Hat s'engage à remplacer le langage problématique dans notre code, notre documentation et nos propriétés Web. Pour plus de détails, consultez le Blog Red Hat.

À propos de Red Hat

Nous proposons des solutions renforcées qui facilitent le travail des entreprises sur plusieurs plates-formes et environnements, du centre de données central à la périphérie du réseau.

Theme

© 2025 Red Hat