activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARTEMIS-898) Artemis Plugin Support
Date Mon, 08 May 2017 13:07:04 GMT

    [ https://issues.apache.org/jira/browse/ARTEMIS-898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000704#comment-16000704
] 

ASF GitHub Bot commented on ARTEMIS-898:
----------------------------------------

GitHub user cshannon opened a pull request:

    https://github.com/apache/activemq-artemis/pull/1257

    ARTEMIS-898 - Adding support for XML configuration of Broker Plugins

    Broker plugins can now be added to the broker through XML config.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/cshannon/activemq-artemis ARTEMIS-898-XML

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/1257.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1257
    
----
commit 9ae945476253c5664e07edfbbf4adbe4d84e25d0
Author: Christopher L. Shannon (cshannon) <christopher.l.shannon@gmail.com>
Date:   2017-05-08T13:04:16Z

    ARTEMIS-898 - Adding support for XML configuration of Broker Plugins
    
    Broker plugins can now be added to the broker through XML config.

----


> Artemis Plugin Support
> ----------------------
>
>                 Key: ARTEMIS-898
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-898
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>          Components: Broker
>    Affects Versions: 2.next
>            Reporter: Matt Pavlovich
>            Assignee: Christopher L. Shannon
>             Fix For: 2.next
>
>
> 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



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message