[CONF] Apache Camel: Implementing Virtual Topics on other JMS providers (page edited)

[confluence]

Page Edited : CAMEL : Implementing Virtual Topics on other JMS providers Implementing Virtual Topics on other JMS providers has been edited by James Strachan (Oct 03, 2008). (View changes) Content: Implementing Virtual Topics on other JMS providers ActiveMQ supports Virtual Topics since durable topic subscriptions kinda suck (see this page for more detail) mostly since they don't support Competing Consumers. Most folks want Queue semantics when consuming messages; so that you can support Competing Consumers for load balancing along with things like Message Groups and Exclusive Consumers to preserve ordering or partition the queue across consumers. However if you are using another JMS provider you can implement Virtual Topics by switching to ActiveMQ or you can use the following Camel pattern. First here's the ActiveMQ approach. send to activemq:topic:VirtualTopic.Orders for consumer A consume from activemq:Consumer.A.VirtualTopic.Orders When using another message broker use the following pattern send to jms:Orders add this route with a to() for each logical durable topic subscriber from("jms:Orders").to("jms:Consumer.A", "jms:Consumer.B", ...); for consumer A consume from jms:Consumer.A

Powered by Atlassian Confluence (Version: 2.2.9 Build:#527 Sep 07, 2006) - Bug/feature request

Unsubscribe or edit your notifications preferences