[CONF] Apache Camel > Publish Subscribe Channel

[confluence]

Publish Subscribe Channel Page edited by Claus Ibsen Changes (3) h3. Publish Subscribe Channel Camel supports the [Publish Subscribe Channel|http://www.enterpriseintegrationpatterns.com/PublishSubscribeChannel.html] from the [EIP patterns|Enterprise Integration Patterns] using for example the following components: * [JMS] for working with JMS Topics for high performance, clustering and load balancing * [XMPP] when using rooms for group communication * [SEDA] for working with SEDA in the same [CamelContext] which can work in pub-sub, but allowing multiple consumers. * [VM] as SEDA but for intra-JVM. !http://www.enterpriseintegrationpatterns.com/img/PublishSubscribeSolution.gif! ... *Using the [Fluent Builders]* {snippet:id=e8|lang=java|url=""> {snippet:id=multicast|lang=java|url=""> *Using the [Spring XML Extensions]* ... Full Content Publish Subscribe Channel Camel supports the Publish Subscribe Channel from the EIP patterns using for example the following components: JMS for working with JMS Topics for high performance, clustering and load balancing XMPP when using rooms for group communication SEDA for working with SEDA in the same CamelContext which can work in pub-sub, but allowing multiple consumers. VM as SEDA but for intra-JVM. Using Routing Logic Another option is to explicitly list the publish-subscribe relationship in your routing logic; this keeps the producer and consumer decoupled but lets you control the fine grained routing configuration using the DSL or Xml Configuration. Using the Fluent Builders RouteBuilder builder = new RouteBuilder() { public void configure() { errorHandler(deadLetterChannel("mock:error")); from("seda:a") .multicast().to("seda:b", "seda:c", "seda:d"); } }; Using the Spring XML Extensions <camelContext errorHandlerRef="errorHandler" xmlns="http://camel.apache.org/schema/spring"> <route> <from uri="seda:a"/> <multicast> <to uri="seda:b"/> <to uri="seda:c"/> <to uri="seda:d"/> </multicast> </route> </camelContext> Using This Pattern If you would like to use this EIP Pattern then please read the Getting Started, you may also find the Architecture useful particularly the description of Endpoint and URIs. Then you could try out some of the Examples first before trying this pattern out. Change Notification Preferences View Online | View Changes | Add Comment