[jboss-jira] [JBoss JIRA] (WFCORE-1161) Simplification of setCapabilityReference where resource only exposes a single capability.

[Tomaz Cerar (JIRA)]

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

Tomaz Cerar commented on WFCORE-1161:
-------------------------------------

In cases where more than one capability is produced, you should produce "wrapper" capability that than exposes all other capabilities.
This was decided to eliminate extremely complex scenarios and problems with resolution that would otherwise occur.

It was also discussed in depth on mailing list.

> Simplification of setCapabilityReference where resource only exposes a single capability.
> -----------------------------------------------------------------------------------------
>
>                 Key: WFCORE-1161
>                 URL: https://issues.jboss.org/browse/WFCORE-1161
>             Project: WildFly Core
>          Issue Type: Enhancement
>          Components: Domain Management
>            Reporter: Darran Lofthouse
>            Assignee: Brian Stansberry
>              Labels: affects_elytron
>             Fix For: 3.0.0.Alpha1
>
>
> Currently we need to use the following method to specify that one of our attributes is a reference to another capability: -
> {code}
>     public BUILDER setCapabilityReference(String referencedCapability, String dependentCapability, boolean dynamicDependent) {
>         referenceRecorder = new CapabilityReferenceRecorder.DefaultCapabilityReferenceRecorder(referencedCapability, dependentCapability, dynamicDependent);
>         return (BUILDER) this;
>     }
> {code}
> However the resource has already indicated the capability it provides and indicated whether it is dynamic so the last two parameters duplicate this information.
> This makes it much harder to re-use attribute definitions across different resources as even though they may reference the same time they now contain information about the resource they are used within.
> As discussed previously there is still the case that a single resource could provide multiple capabilities and this additional information may be required to clarify which capability it is in relation to but in general if a resource only provides a single capability we should be able to detect that without the additional information on the attribute.



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