[
https://issues.apache.org/jira/browse/ARTEMIS-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14586762#comment-14586762
]
Justin Bertram commented on ARTEMIS-92:
---------------------------------------
I'm adding the following methods to
{{org.apache.activemq.artemis.core.server.ServiceRegistry}}:
{noformat}
void addDivertTransformer(String name, Transformer transformer);
void removeDivertTransformer(String name);
Transformer getDivertTransformer(String name);
void addBridgeTransformer(String name, Transformer transformer);
void removeBridgeTransformer(String name);
Transformer getBridgeTransformer(String name);
{noformat}
> 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
> Assignee: Justin Bertram
> Fix For: 1.0.1
>
>
> 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)
