[
https://issues.apache.org/jira/browse/ARTEMIS-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16574389#comment-16574389
]
ASF GitHub Bot commented on ARTEMIS-2018:
-----------------------------------------
Github user michaelandrepearce commented on the issue:
https://github.com/apache/activemq-artemis/pull/2229
Looks good to me.
Not to affect this PR, but a general comment that we should start thinking
about, there now is a case that by having one broker plugin that it will be
invoked left right and centre on every intercept, e.g. say i want to have
broker plugin to capture something not on the hotpath, the plugin will still be
called on the hotpath, as the checks done in the if statement are simply
hasBrokerPlugins, i wonder if we could make it some time to have the
"hasBrokerPlugins" to have specific types, where when the plugin is added it
registers the types its applicable for, and thus later we could have
"hasBrokerPluginsBridgeType" and "hasBrokerPluginsBindingType".
> 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)
