You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Matt Pavlovich (JIRA)" <ji...@apache.org> on 2016/12/20 16:08:58 UTC

[jira] [Created] (ARTEMIS-898) Artemis Plugin Support

Matt Pavlovich created ARTEMIS-898:
--------------------------------------

             Summary: Artemis Plugin Support
                 Key: ARTEMIS-898
                 URL: https://issues.apache.org/jira/browse/ARTEMIS-898
             Project: ActiveMQ Artemis
          Issue Type: New Feature
          Components: Broker
            Reporter: Matt Pavlovich


ActiveMQ 5.x currently has a number of extension points via Plugins, or simple Spring bean wiring. Artemis should provide extension points to meet various requirements.

The protocol interceptors are handy, but also limiting in that each plugin would need to be implemented for every protocol. Feels like there should be defined extension point(s) within the broker.

Core Broker Plugins:
1. Message header / property manipulation
2. Message body manipulation
3. Activity tracing (broker becomes master, network bridge start/stop, message rcv/sent/ack/rollback, consumer/producer add/remove, broker add/remove, destination add/remove, connection add/remove, fast producer/slow consumer, etc)
   a. Audit / trace logs
   b. Triggers based on events

ref: http://activemq.apache.org/maven/apidocs/org/apache/activemq/broker/MutableBrokerFilter.html

Additional extension point:
 DestinationPolicies: Ability to impact destination behaviors for dispatch, subscription policies, etc.

Side benefit regarding Advisory Support:
If the plugin framework can get squared away, an upside could be that Advisory support becomes a plugin vs an ingrained feature and we could have more control over configuration and behavior.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)