Uploaded image for project: 'ActiveMQ Artemis'
  1. ActiveMQ Artemis
  2. ARTEMIS-898

Artemis Plugin Support

    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.1.0
    • 2.1.0
    • Broker
    • None

    Description

      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.

      From ARTEMIS-17

      Support for using Camel as an interceptor/plugin

      Attachments

        Issue Links

          Activity

            People

              cshannon Christopher L. Shannon
              mattrpav Matt Pavlovich
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: