You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "clebert suconic (JIRA)" <ji...@apache.org> on 2015/06/03 23:33:38 UTC

[jira] [Commented] (ARTEMIS-92) Inject divert and bridge transformer classes

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

clebert suconic commented on ARTEMIS-92:
----------------------------------------

[~jmesnil] What do you suggest? We could have an add transformer method on the Registry you mentioned, and whenever a class with that name is found we could just use that one. Any idea?

> Inject divert and bridge transformer classes
> --------------------------------------------
>
>                 Key: ARTEMIS-92
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-92
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>    Affects Versions: 1.0.0
>            Reporter: Jeff Mesnil
>
> Divert and bridges can have a transformer classes.
> They are specified in the divert and bridges configuration using class names and loads by Artemis when its server is started.
> However in a modular environment (such as WildFly), Artemis may not be aware of the modules containing the loaded classes (that can come from the user space).
> It is not suitable to have the ActiveMQ module depends on these user modules (as it breaks any modularity). Instead ActiveMQ should be able to use transformer *instances* (loaded by WildFly) from the divert and bridge classes.
> There is already such a mechanism for loaded classes such as server interceptor and connector services through the ServiceRegistry.
> This class should be extended to also work with divert and bridge transformers.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)