[ https://issues.jboss.org/browse/WFLY-6269?page=com.atlassian.jira.plugin.... ] Jeff Mesnil edited comment on WFLY-6269 at 3/1/16 4:12 AM: ----------------------------------------------------------- There is a global solution that would work in all cases: add an optional module dependency to org.apache.activemq.artemis module (eg named "org.apache.activemq.artemis.addons"). Since it is an optional module, it does not require to exist. If users wants to specify specific classes in Artemis, they could create this module and add the classes to it so that Artemis could load them. This also make sure that the user does not have to edit org.apache.activemq.artemis own module definition (which prevents patching to work). Ideally, all the resources that requires to load classes should define both a class name and a module. In practice, this is important for the transformers of the divert and bridge resources and the connector-services. This is less important for the connector/acceptor (the implementations are so complex, I've never see anybody specifying something other than Artemis own implementations) and connection-load-balancing-policy-class-name. Changing these resource definitions is more involving (it requires new management versions, XSD, transformers, etc.) and would be better addressed in WFLY 11.x. The global solution of adding an optional module can be done in WFLY 10.x timeframe and will not prevent refining the resources later on. was (Author: jmesnil): There is a global solution that would work in all cases: add an optional module dependency to org.apache.activemq.artemis module (eg named "org.apache.activemq.artemis.addons"). Since it is an optional module, it does not require to exist. If users wants to specify specific classes in Artemis, they could create this module and add the classes to it so that Artemis could load them. This also make sure that the user does not have to edit org.apache.activemq.artemis own module definition (which prevents patching to work). Ideally, all the resources that requires to load classes should define both a class name and a module. In practice, this is important for the transformers of the divert and bridge resources. This is less important for the connector/acceptor (the implementations are so complex, I've never see anybody specifying something other than Artemis own implementations) and connection-load-balancing-policy-class-name. Changing these resource definitions is more involving (it requires new management versions, XSD, transformers, etc.) and would be better addressed in WFLY 11.x. The global solution of adding an optional module can be done in WFLY 10.x timeframe and will not prevent refining the resources later on. -- This message was sent by Atlassian JIRA (v6.4.11#64026)