[
https://issues.jboss.org/browse/WFCORE-840?page=com.atlassian.jira.plugin...
]
Brian Stansberry commented on WFCORE-840:
-----------------------------------------
I'm going to "reject" the pull request just to get this into the correct
state. Unfortunately, JIRA is now "helping" us manage issue state transitions by
scanning commit messages in PRs, so please be cautious about referencing JIRA #s if the
commit doesn't actually resolve the issue.
If a resource provides 2 capabilities, and its config includes a model ref attribute is
only relevant to one, then it is incorrect to record that both capabilities require the
dependee.
I'm going to unschedule this. It's an interesting thing to consider, but not a
current priority.
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
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)