[jboss-jira] [JBoss JIRA] (WFCORE-960) CapabilityRegistryResourceDefinition is ignoring CapabilityScope in its reporting

[Brian Stansberry (JIRA)]

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

Brian Stansberry updated WFCORE-960:
------------------------------------
    Fix Version/s: 3.0.0.Alpha2
                       (was: 3.0.0.Alpha1)


> CapabilityRegistryResourceDefinition is ignoring CapabilityScope in its reporting
> ---------------------------------------------------------------------------------
>
>                 Key: WFCORE-960
>                 URL: https://issues.jboss.org/browse/WFCORE-960
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Domain Management
>    Affects Versions: 2.0.0.Beta6
>            Reporter: Brian Stansberry
>            Assignee: Tomaz Cerar
>             Fix For: 3.0.0.Alpha2
>
>
> The keys for the different registrations in the CapabilityRegistry is their id, which is a combination of their name and their CapabilityScope. CapabilityRegistryResourceDefinition when it reports the registrations is ignoring the scope.
> For WildFly Core 2.0.0.CR1 I'm going to disable registration of CapabilityRegistryResourceDefinition. We don't have specific management client use of this management API yet and it can still use some massaging, so committing ourselves to supporting the current API for many years isn't worth it.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)