Return-Path: Delivered-To: apmail-geronimo-activemq-commits-archive@www.apache.org Received: (qmail 45119 invoked from network); 2 Feb 2006 16:36:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 2 Feb 2006 16:36:10 -0000 Received: (qmail 77835 invoked by uid 500); 2 Feb 2006 16:35:54 -0000 Delivered-To: apmail-geronimo-activemq-commits-archive@geronimo.apache.org Received: (qmail 77813 invoked by uid 500); 2 Feb 2006 16:35:53 -0000 Mailing-List: contact activemq-commits-help@geronimo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: activemq-dev@geronimo.apache.org Delivered-To: mailing list activemq-commits@geronimo.apache.org Received: (qmail 77804 invoked by uid 99); 2 Feb 2006 16:35:53 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Feb 2006 08:35:53 -0800 X-ASF-Spam-Status: No, hits=-9.4 required=10.0 tests=ALL_TRUSTED,NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [209.237.227.194] (HELO minotaur.apache.org) (209.237.227.194) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 02 Feb 2006 08:35:39 -0800 Received: (qmail 44517 invoked by uid 65534); 2 Feb 2006 16:35:17 -0000 Message-ID: <20060202163517.44503.qmail@minotaur.apache.org> Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r374430 [9/45] - /incubator/activemq/site/ Date: Thu, 02 Feb 2006 16:33:52 -0000 To: activemq-commits@geronimo.apache.org From: jstrachan@apache.org X-Mailer: svnmailer-1.0.5 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Added: incubator/activemq/site/Composite+Destinations URL: http://svn.apache.org/viewcvs/incubator/activemq/site/Composite%2BDestinations?rev=374430&view=auto ============================================================================== --- incubator/activemq/site/Composite+Destinations (added) +++ incubator/activemq/site/Composite+Destinations Thu Feb 2 08:31:10 2006 @@ -0,0 +1,247 @@ + + + + + + + + ActiveMQ - Composite Destinations + + + + + + + + + + + + + + + +
+ + + + + + +
+

Overview

+ +

Community

+ +

Using ActiveMQ

+ +

Features

+ +

Connectivitiy

+ +

Utilities

+ +

External Tools

+ +

Related Projects

+ +

Support

+ +

Developers

+ +

Tools we use

 + +

Feeds

+ + + + + + + + + +
+
+ 		+ Site +
+ + + News +
+ 		+ +
+ + + + + +
+ Composite Destinations + + +
+
+ + +
+
+

As of version 1.1, ActiveMQ supports a technology we call composite destinations. This allows a single virtual JMS Destination to be used to represent a collection of JMS Destinations.

+

For example you can use composite destinations to send a message to 12 physical queues in one operation. Or send a message to one topic and one queue in one operation.

+

We do this using a simple separator of "," allowing a number of destinations to be specified when creating a destintation, or registering destinations in JNDI. e.g. the destination

+

+

+ 
FOO.A,FOO.B,FOO.C
+
+

+

Represents 3 different destinations. This could be used with a queue or topic to represent a set of 3 destinations. e.g.

+

+

+ 
// send to 3 queues as one logical operation
+Queue queue = new ActiveMQQueue("FOO.A,FOO.B,FOO.C");
+producer.send(queue, someMessage);
+
+

+

If you wish to mix and match the types of destination, you can use a prefix of queue:// or topic:// to differentiate the type of destination. e.g. to publish on a queue but also make a notification on a topic as well you could use

+

+

+ 
// send to queues and topic one logical operation
+Queue queue = new ActiveMQQueue("FOO.A,topic://NOTIFY.FOO.A");
+producer.send(queue, someMessage);
+
+

+
+
+ +   +