[jboss-jira] [JBoss JIRA] (WFCORE-840) Improve API on AttributeDefinitions where a capability is referenced.
[
https://issues.jboss.org/browse/WFCORE-840?page=com.atlassian.jira.plugin...
]
Darran Lofthouse commented on WFCORE-840:
-----------------------------------------
As the name of the capability and the return type of the service are two independent
things I think we could have a case where one resource has two capabilities backed by one
service.
However the most pressing case that I think most will encounter is the single resource,
single capability, single service - and currently has the attribute definition also
needing to duplicate specifying the capability of the resource.
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
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)