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

[Tomaz Cerar (JIRA)]

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

Tomaz Cerar commented on WFCORE-840:
------------------------------------

It somewhat relates, as api for automatic registration of capabilities that are defined on RD was added.

Which was also one of the things that help fix this.
with current state of API one can register as many capabilities he wants, even if they are not related to single attribute.



> 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)