activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARTEMIS-898) Artemis Plugin Support
Date Wed, 03 May 2017 16:18:04 GMT

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

ASF subversion and git services commented on ARTEMIS-898:
---------------------------------------------------------

Commit 1e1ede84c0483099f27741bc046ef95c08e1d090 in activemq-artemis's branch refs/heads/master
from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=1e1ede8 ]

ARTEMIS-898 - Adding Plugin Support

Adding a new ActievMQServerPlugin interface to support adding custom
behavior to the broker at certain events such as connection or session
creation.

https://issues.apache.org/jira/browse/ARTEMIS-898


> 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