[jboss-jira] [JBoss JIRA] (WFCORE-840) Improve API on AttributeDefinitions where a capability is referenced.

[Brian Stansberry (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107246#comment-13107246 ] 

Brian Stansberry commented on WFCORE-840:
-----------------------------------------

How did https://github.com/wildfly/wildfly-core/pull/1029 relate to this?

We need to track the dependencies between capabilities. Perhaps some other way will work, but since the resource that has this attribute can provide > 1 capability, or even in theory it could be a parent resource that provides the capability, in at least some cases we need some way to clarify the dependent side.

> Improve API on AttributeDefinitions where a capability is referenced.
> ---------------------------------------------------------------------
>
>                 Key: WFCORE-840
>                 URL: https://issues.jboss.org/browse/WFCORE-840
>             Project: WildFly Core
>          Issue Type: Sub-task
>          Components: Domain Management
>    Affects Versions: 2.0.0.Alpha11
>            Reporter: Darran Lofthouse
>            Assignee: Tomaz Cerar
>             Fix For: 2.0.0.CR1
>
>
> Take the following method call defining an attribute: -
> {code}
> .setCapabilityReference(PROVIDERS_CAPABILITY, SASL_SERVER_FACTORY_CAPABILITY, true)
> {code}
> This definition says this attribute references something which provides the PROVIDERS_CAPABILITY.
> However it also states that the resource that contains this attributes provides the SASL_SERVER_FACTORY_CAPABILITY.
> Really what the resource provides is not directly related to this attribute definition.
> The following pull request has already improved on registering in advance what capability a resource can provide: -
> https://github.com/wildfly/wildfly-core/pull/909



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