[
https://issues.apache.org/jira/browse/ARTEMIS-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16574585#comment-16574585
]
ASF GitHub Bot commented on ARTEMIS-2018:
-----------------------------------------
Github user cshannon commented on the issue:
https://github.com/apache/activemq-artemis/pull/2229
I like the idea of using separate interfaces and having
ActiveMQServerPlugin extend them. This way if someone doesn't care they can
make it easy and just extend ActiveMQServerPlugin (as well as keep backwards
compatibility) or the user can choose to pick specific interfaces for
performance.
> 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)
