[
https://issues.jboss.org/browse/WFLY-6269?page=com.atlassian.jira.plugin....
]
Lin Gao commented on WFLY-6269:
-------------------------------
There are some other {{class}} related attributes defined too in
wildfly-messaging-activemq_1_0.xsd:
* {{factory-class}} in element: {{connector}}
* {{factory-class}} in element: {{acceptor}}
* {{transformer-class-name}} in element: {{divert}}
* {{transformer-class-name}} in element: {{bridge}}
* {{connection-load-balancing-policy-class-name}} in element:
{{legacy-connection-factory}}
* {{connection-load-balancing-policy-class-name}} in element: {{connection-factory}}
* {{connection-load-balancing-policy-class-name}} in element:
{{pooled-connection-factory}}
Should we define a module for these cases too? Is there an global way to solve this or we
only fix this case by case?
connector-service resource does not define a module for the classes
to load
---------------------------------------------------------------------------
Key: WFLY-6269
URL:
https://issues.jboss.org/browse/WFLY-6269
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 10.0.0.Final
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
The connector-service resource has only a factory-class attribute and does not specify
from which module the class should be loaded.
{noformat}
<connector-service name="b"
factory-class="bar.foo">
<param name="foo"
value="${connector.value:bar}"/>
<param name="bar"
value="2"/>
</connector-service>
{noformat}
This means that the module defining the class must be a dependency of the
org.apache.activemq.artemis module since it's Artemis that currently loads it.
A module attribute should be added so that the class could be loaded from any module.
The messaging-activemq subsystem would then be able to load it and pass it to
Artemis's ServiceRegistry (similarly to the interceptors).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)