activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino (JIRA)" <>
Subject [jira] [Resolved] (APLO-71) Apollo plugins should be easy to configure
Date Thu, 11 Aug 2011 18:42:28 GMT


Hiram Chirino resolved APLO-71.

       Resolution: Fixed
    Fix Version/s: 1.0-beta5
         Assignee: Hiram Chirino

I've changed how service plugins are configured so that you can embed additional configuration
data for each service plugin.

I've documented how the service plugins work at:

I've also extend the configuration model so that you can add additional user defined data
to broker, virtual host, connector, and destination objects.  The additional data is not used
by the broker, but could be potentially used as configuration data for plugins.

> Apollo plugins should be easy to configure
> ------------------------------------------
>                 Key: APLO-71
>                 URL:
>             Project: ActiveMQ Apollo
>          Issue Type: Improvement
>            Reporter: Lionel Cons
>            Assignee: Hiram Chirino
>             Fix For: 1.0-beta5
> 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:


View raw message