[jboss-jira] [JBoss JIRA] (WFCORE-1161) Simplification of setCapabilityReference where resource only exposes a single capability.
Brian Stansberry (JIRA)
issues at jboss.org
Mon Nov 30 14:55:00 EST 2015
[ https://issues.jboss.org/browse/WFCORE-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Stansberry updated WFCORE-1161:
-------------------------------------
Fix Version/s: 3.0.0.Alpha1
> 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)
More information about the jboss-jira
mailing list