]
Brian Stansberry resolved WFCORE-840.
-------------------------------------
Resolution: Out of Date
The unambiguous case no longer requires you to provide the name of the dependent
capability.
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: Enhancement
Components: Domain Management
Affects Versions: 2.0.0.Alpha11
Reporter: Darran Lofthouse
Assignee: Tomaz Cerar
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