[
https://issues.apache.org/jira/browse/ARTEMIS-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575576#comment-16575576
]
ASF subversion and git services commented on ARTEMIS-2019:
----------------------------------------------------------
Commit 19e1bbeb49ced9a8f7b5be09148ba27b53af3172 in activemq-artemis's branch
refs/heads/master from [~teaandcoffee]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=19e1bbe ]
ARTEMIS-2019 - Seperate ServerPlugin Interfaces
Seperate plugin interface by area, all extending a base interface.
Update code to check and call only plugins implementing specific interfaces.
Existing interface extends all the new interfaces for back compatibility or
those who want simplicity and don't care about perf.
> Refactor Artemis ServerPlugin to Seperate concerns
> --------------------------------------------------
>
> Key: ARTEMIS-2019
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2019
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Michael Andre Pearce
> Priority: Major
>
> Currently ServerPlugins all have to implement ActiveMQServerPlugin which
> means if someone wants to have a plugin to get a callback say on connection,
> it will mean else where on hot paths where a check is done to eliminate
> overhead, the plugin will be called even if the user doesnt want it to be.
> As such refactor to separate interfaces by plugin area so that users can
> implement just the area they wish without needing to worry about it impacting
> other areas.
>
>
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
