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

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

GitHub user cshannon opened a pull request:

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

    ARTEMIS-2018 - Add bridge events to plugin API

    Add callbacks to handle bridge events including beforeDeliverBridge,
    afterDeliverBridge and afterAcknowledgeBridge

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

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

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

    https://github.com/apache/activemq-artemis/pull/2229.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 #2229
    
----
commit 95ff39f6bfae9c51e6c3c1d1ac2782f60f5d2daa
Author: Christopher L. Shannon (cshannon) <christopher.l.shannon@...>
Date:   2018-08-08T18:10:22Z

    ARTEMIS-2018 - Add bridge events to plugin API
    
    Add callbacks to handle bridge events including beforeDeliverBridge,
    afterDeliverBridge and afterAcknowledgeBridge

----


> Artemis ServerPlugin support for Bridging events
> ------------------------------------------------
>
>                 Key: ARTEMIS-2018
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2018
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 2.6.2
>            Reporter: Christopher L. Shannon
>            Assignee: Christopher L. Shannon
>            Priority: Major
>             Fix For: 2.7.0, 2.6.3
>
>
> It would be useful to have plugin hooks for certain events when using a 
> bridge both by itself and in a cluster.  The three initial ones I have in 
> mind are beforeDeliverBridge, afterDeliverBridge and afterAcknowledgeBridge 
> but more could easily be added in the future if necessary.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to