activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (ARTEMIS-898) Artemis Plugin Support
Date Tue, 02 May 2017 19:18:04 GMT


ASF GitHub Bot commented on ARTEMIS-898:

Github user cshannon commented on the issue:
    @clebertsuconic - I just ran my new tests and the sanity check as I figured the complete
test suite takes a long time to run so I was going to let Jenkins run it. So up to you if
you just want to go ahead with 2.1.0 without this patch or wait for CI to run the test suite
and merge it in. I'm ok with either way.

> Artemis Plugin Support
> ----------------------
>                 Key: ARTEMIS-898
>                 URL:
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>          Components: Broker
>            Reporter: Matt Pavlovich
>             Fix For:
> 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:
> 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

View raw message