Red Hat Summit Red Hat SummitSupportKonsoleEntwicklerDemo startenKontakt

Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.

5.2. Publish-Subscribe Channel

Overview
Link kopieren

A publish-subscribe channel, shown in Figure 5.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 5.2. Publish Subscribe Channel Pattern

Publish subscribe channel pattern
View larger image
Publish subscribe channel pattern

Components that support publish-subscribe channel
Link kopieren

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
Link kopieren

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 "EIP Component Reference" for more details.

ActiveMQ
Link kopieren

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 "EIP Component Reference" for more details.

XMPP
Link kopieren

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

Static subscription lists
Link kopieren

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
Link kopieren

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
Link kopieren

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
Nach oben
Red Hat logoGithubredditYoutubeTwitter

Lernen

Testen, kaufen und verkaufen

Communitys

Über Red Hat Dokumentation

Wir helfen Red Hat Benutzern, mit unseren Produkten und Diensten innovativ zu sein und ihre Ziele zu erreichen – mit Inhalten, denen sie vertrauen können. Entdecken Sie unsere neuesten Updates.

Mehr Inklusion in Open Source

Red Hat hat sich verpflichtet, problematische Sprache in unserem Code, unserer Dokumentation und unseren Web-Eigenschaften zu ersetzen. Weitere Einzelheiten finden Sie in Red Hat Blog.

Über Red Hat

Wir liefern gehärtete Lösungen, die es Unternehmen leichter machen, plattform- und umgebungsübergreifend zu arbeiten, vom zentralen Rechenzentrum bis zum Netzwerkrand.

Theme

© 2025 Red Hat