[
https://issues.jboss.org/browse/WFLY-10634?page=com.atlassian.jira.plugin...
]
Radoslav Husar updated WFLY-10634:
----------------------------------
Description:
The mod_cluster custom load metrics classes are loaded from the subsystem classloader
which requires users to tinker with our module structure. This is wrong since there is no
way to specify which module to use.
We should just expose {{module}} attribute on the custom load metric (defaults to current
default which is mod_cluster module, so no compatibility issues).
was:
The mod_cluster custom load metrics classes are loaded from the subsystem classloader
which requires users to tinker with our module structure. This is wrong.
We should just expose {{module}} attribute on the custom load metric (defaults to current
default which is mod_cluster module, so no compatibility issues).
mod_cluster custom load metric classes are loaded from the subsystem
classloader
--------------------------------------------------------------------------------
Key: WFLY-10634
URL:
https://issues.jboss.org/browse/WFLY-10634
Project: WildFly
Issue Type: Bug
Components: mod_cluster
Affects Versions: 13.0.0.Final
Reporter: Radoslav Husar
Assignee: Radoslav Husar
The mod_cluster custom load metrics classes are loaded from the subsystem classloader
which requires users to tinker with our module structure. This is wrong since there is no
way to specify which module to use.
We should just expose {{module}} attribute on the custom load metric (defaults to current
default which is mod_cluster module, so no compatibility issues).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)