Mailing-List: contact commits-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Mon, 8 Aug 2011 13:54:27 +0000 (UTC)
From: "Lionel Cons (JIRA)" <jira@apache.org>
To: commits@activemq.apache.org
Message-ID: 
 <187838936.16588.1312811667169.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (APLO-71) Apollo plugins should be easy to
 configure
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Apollo plugins should be easy to configure
------------------------------------------

                 Key: APLO-71
                 URL: https://issues.apache.org/jira/browse/APLO-71
             Project: ActiveMQ Apollo
          Issue Type: Improvement
            Reporter: Lionel Cons


Apollo already supports some kind of plugins although this is not yet documented (see APLO-28). These plugins should be easy to configure.

Like for ActiveMQ, the easiest way is probably to be able to put in the apollo.xml file some elements which are plugin specific.

The simplest approach would be a single plugin sub-tree (like in activemq.xml's broker.plugins).

However, it would be very cool to be able to attach plugin specific information to a destination element and be able to reuse Apollo's destination matching (= the first matching element is used).

Also, it would be good to be able to handle the configuration updates like the rest of Apollo: the plugin should be able to know if/when its configuration has changed.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira