[jboss-jira] [JBoss JIRA] (WFCORE-1507) Expose features currently provided by ModelController via capabilities usable by extensions

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/WFCORE-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry updated WFCORE-1507:
-------------------------------------
    Description: 
-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.-

Extensions may have a need to create an internal ModelControllerClient or to register notification handlers. Currently this is done by looking up the ModelController via its internal service name but:

1) ModelController exposes methods that should not be available to extensions
2) Accessing services should be via a capability.

So, we need to expose capabilities for these functions.

  was: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.



> Expose features currently provided by ModelController via capabilities usable by extensions
> -------------------------------------------------------------------------------------------
>
>                 Key: WFCORE-1507
>                 URL: https://issues.jboss.org/browse/WFCORE-1507
>             Project: WildFly Core
>          Issue Type: Enhancement
>          Components: Domain Management
>            Reporter: Brian Stansberry
>            Assignee: 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.-
> Extensions may have a need to create an internal ModelControllerClient or to register notification handlers. Currently this is done by looking up the ModelController via its internal service name but:
> 1) ModelController exposes methods that should not be available to extensions
> 2) Accessing services should be via a capability.
> So, we need to expose capabilities for these functions.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)