Return-Path: Delivered-To: apmail-geronimo-activemq-commits-archive@www.apache.org Received: (qmail 48270 invoked from network); 27 Jul 2006 16:00:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 27 Jul 2006 16:00:27 -0000 Received: (qmail 90305 invoked by uid 500); 27 Jul 2006 16:00:27 -0000 Delivered-To: apmail-geronimo-activemq-commits-archive@geronimo.apache.org Received: (qmail 90266 invoked by uid 500); 27 Jul 2006 16:00:27 -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 90257 invoked by uid 99); 27 Jul 2006 16:00:27 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Jul 2006 09:00:27 -0700 X-ASF-Spam-Status: No, hits=-9.4 required=10.0 tests=ALL_TRUSTED,NO_REAL_NAME X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [140.211.166.113] (HELO eris.apache.org) (140.211.166.113) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Jul 2006 09:00:25 -0700 Received: by eris.apache.org (Postfix, from userid 65534) id 372481A981A; Thu, 27 Jul 2006 09:00:05 -0700 (PDT) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r426110 - in /incubator/activemq/site: community.html configure-startup-destinations.html features.html how-do-i-create-new-destinations.html new-features-in-41.html Date: Thu, 27 Jul 2006 16:00:04 -0000 To: activemq-commits@geronimo.apache.org From: chirino@apache.org X-Mailer: svnmailer-1.0.8 Message-Id: <20060727160005.372481A981A@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Author: chirino Date: Thu Jul 27 09:00:03 2006 New Revision: 426110 URL: http://svn.apache.org/viewvc?rev=426110&view=rev Log: Latest export from confluence Added: incubator/activemq/site/configure-startup-destinations.html Modified: incubator/activemq/site/community.html incubator/activemq/site/features.html incubator/activemq/site/how-do-i-create-new-destinations.html incubator/activemq/site/new-features-in-41.html Modified: incubator/activemq/site/community.html URL: http://svn.apache.org/viewvc/incubator/activemq/site/community.html?rev=426110&r1=426109&r2=426110&view=diff ============================================================================== --- incubator/activemq/site/community.html (original) +++ incubator/activemq/site/community.html Thu Jul 27 09:00:03 2006 @@ -285,16 +285,16 @@ Hide Children + + + + + \ No newline at end of file Modified: incubator/activemq/site/features.html URL: http://svn.apache.org/viewvc/incubator/activemq/site/features.html?rev=426110&r1=426109&r2=426110&view=diff ============================================================================== --- incubator/activemq/site/features.html (original) +++ incubator/activemq/site/features.html Thu Jul 27 09:00:03 2006 @@ -274,7 +274,7 @@ -
+
-
-

In ActiveMQ you do not have to create destinations up front before you can use them. Just create a destination dynamically either by

+

In ActiveMQ you do not have to create destinations up front before you can use them. Just create a destination dynamically either by

  • calling createQueue() or createTopic() on a JMS Session
    • @@ -287,6 +286,12 @@

    The ActiveMQ broker auto-creates the physical resources associated with a destination on demand (i.e. when messages are sent to a new destination on a broker). This means that a client can create a new Queue or Topic as above and the broker will automatically create the physical destinations for you. This avoids spending large amounts of time creating every individual destination you wish to use and possibly then exposing it in some JNDI provider.

    +

    Creating destinations on startup

    + +

    Its completely optional but as of 4.1 you can Configure Startup Destinations to specify which destinations are automatically created when the broker starts.

    + +

    Limiting creation of destinations

    +

    If you need to restrict access or creation of destinations then please use the Security option to disable destinations being auto-created for certain users.

    Client side destination objects are not the same as server side resources

    Note that the ActiveMQ Broker will only create server side resources for destinations when messages are actually sent to them. So you can create as many instances of ActiveMQTopic and ActiveMQQueue on a client without any real overhead until you actually send messages to them on a broker. So a JMS client creating a new ActiveMQQueue POJO does not mean you are creating server side queue resources.

    @@ -304,8 +309,8 @@ Modified: incubator/activemq/site/new-features-in-41.html URL: http://svn.apache.org/viewvc/incubator/activemq/site/new-features-in-41.html?rev=426110&r1=426109&r2=426110&view=diff ============================================================================== --- incubator/activemq/site/new-features-in-41.html (original) +++ incubator/activemq/site/new-features-in-41.html Thu Jul 27 09:00:03 2006 @@ -280,6 +280,7 @@
  • Shared File System Master Slave
  • JDBC Master Slave
  • Virtual Destinations
    • +
  • Configure Startup Destinations
  • Structured Message Properties and MapMessages
    • @@ -293,7 +294,10 @@ Hide Children