[jboss-jira] [JBoss JIRA] (WFCORE-4626) Expose ExternalModuleService as WildFly capability

[Jeff Mesnil (Jira)]

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

Jeff Mesnil updated WFCORE-4626:
--------------------------------
    Component/s: Management


> Expose ExternalModuleService as WildFly capability
> --------------------------------------------------
>
>                 Key: WFCORE-4626
>                 URL: https://issues.jboss.org/browse/WFCORE-4626
>             Project: WildFly Core
>          Issue Type: Task
>          Components: Management
>            Reporter: Yeray Borges
>            Assignee: Yeray Borges
>            Priority: Major
>             Fix For: 11.0.0.Beta3
>
>
> ExternalModuleService is used to create the ExternalModuleSpecService which exposes the ModuleDefinition for any external module dependency.
> Currently, ExternalModuleService is used via DUPs to scan the deployment and add external modules. We should expose this service via a Capability so it can be easily accessed via not only by the DUPs, but also other services that could require configure external modules.
> This capability should be registered in ServerService, see for example PathManager. It should be something that ExternalModuleService implements, the goal is not to expose the start/stop/getValue methods via the capability.
> See [this|https://github.com/wildfly/wildfly-core/pull/3890#issuecomment-521809295] as reference comment.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)