[
https://issues.jboss.org/browse/WFCORE-1507?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on WFCORE-1507:
------------------------------------------
I think this probably shouldn't expose ModelController. Rather it could be something
like a new "ModelControllerClientFactory" interface that just exposes
createClient. I don't think outsiders need the execute op. JMX needs the execute op so
perhaps we expose ModelController via a cap for that use case, but JMX is semi-kernel. The
main external requirement we're satisfying here is for
"ModelControllerClientFactory".
Expose the ModelController via a capability
-------------------------------------------
Key: WFCORE-1507
URL:
https://issues.jboss.org/browse/WFCORE-1507
Project: WildFly Core
Issue Type: Enhancement
Components: Domain Management
Reporter: Brian Stansberry
A server installs ServerService while an HC installs DomainModelControllerService, under
different service names but both of which implement Service<ModelController>. To
make it easier for subsystems that want ModelController access to work on both a server
and an HC, we should create a capability with service type ModelController and have both
processes use it.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)