[jboss-jira] [JBoss JIRA] (WFCORE-2359) Failure message when an op requires a non-existent capability doesn't list registration points for dynamic caps

ehsavoie Hugonnet (JIRA) issues at jboss.org
Wed Jun 21 13:22:00 EDT 2017


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

ehsavoie Hugonnet reassigned WFCORE-2359:
-----------------------------------------

    Assignee: ehsavoie Hugonnet


> Failure message when an op requires a non-existent capability doesn't list registration points for dynamic caps
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: WFCORE-2359
>                 URL: https://issues.jboss.org/browse/WFCORE-2359
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Domain Management
>            Reporter: Brian Stansberry
>            Assignee: ehsavoie Hugonnet
>
> {code}
> [standalone at embedded /] /socket-binding-group=standard-sockets/socket-binding=test:add(interface=bogus,port=12345)
> {
>     "outcome" => "failed",
>     "failure-description" => "WFLYCTL0369: Required capabilities are not available:
>     org.wildfly.network.interface.bogus; There are no known registration points which can provide this capability.",
>     "rolled-back" => true
> }
> {code}
> The failure message is not fully helpful, since while there are no reg points for org.wildfly.network.interface.bogus there are points for caps whose dynamic part is org.wildfly.network.interface.
> The message is created using the results of CapabilityRegistry.getPossibleProviderPoints(), which just does a map lookup of the passed in capability name.
> Any fix that changes getPossibleProviderPoints() will need to be careful not to break other uses of that method.



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


More information about the jboss-jira mailing list