[
https://issues.jboss.org/browse/WFCORE-4207?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on WFCORE-4207:
------------------------------------------
We need to be careful that this is the right thing to do.
The problem is these are not used as single resource definitions, as they originally were
in the threads subsystem. They are just reusable code.
So, if subsystem X uses this code and creates an executor of some type named
"default" it's not wrong for subsystem Y to also create the same kind of
pool with the same name. But if they end up with the same capability name, that will no
longer work.
Now, it's possible that this was already a problem, as this kind of thing would have
led to a duplicate ServiceName problem. In which case we don't need to worry about it
so much.
Add capabilities in the Thread subsystem resource definitions
-------------------------------------------------------------
Key: WFCORE-4207
URL:
https://issues.jboss.org/browse/WFCORE-4207
Project: WildFly Core
Issue Type: Enhancement
Components: Management
Affects Versions: 7.0.0.Alpha5
Reporter: ehsavoie Hugonnet
Assignee: ehsavoie Hugonnet
Priority: Major
The deprecated thread subsystem resource definitions are used in several subsystems.
Adding support for capabilities should help them get the model validation easier.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)