[jboss-jira] [JBoss JIRA] (WFCORE-1058) Encapsulate logic to specify dynamic capability name resolution from a PathAddress
Paul Ferraro (JIRA)
issues at jboss.org
Wed Oct 14 10:32:00 EDT 2015
[ https://issues.jboss.org/browse/WFCORE-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Ferraro updated WFCORE-1058:
---------------------------------
Description:
One can create a capability whose dynamic name is not resolved using the value of the last element of a path address (e.g. using the value of a parent resource). In this case, the logic for generating the dynamic name need to be modified in multiple places.
# CapabilityReferenceRecorder.DefaultCapabilityReferenceRecorder.getDynamicDependentName(...)
# AbstractAddStepHandler.recordCapabilitiesAndRequirements(...)
# AbstractRemoveStepHandler.recordCapabilitiesAndRequirements(...)
For reference, the clustering subsystems handle this via custom abstraction:
https://github.com/wildfly/wildfly/blob/master/clustering/common/src/main/java/org/jboss/as/clustering/controller/Capability.java
was:
One can create a capability whose dynamic name is not resolved using the value of the last element of a path address (e.g. using the value of a parent resource). In this case, the logic for generating the dynamic name need to be modified in multiple places.
# CapabilityReferenceRecorder.DefaultCapabilityReferenceRecorder.getDynamicDependentName(...)
# AbstractAddStepHandler.recordCapabilitiesAndRequirements(...)
> Encapsulate logic to specify dynamic capability name resolution from a PathAddress
> ----------------------------------------------------------------------------------
>
> Key: WFCORE-1058
> URL: https://issues.jboss.org/browse/WFCORE-1058
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Affects Versions: 2.0.0.CR6
> Reporter: Paul Ferraro
> Assignee: Brian Stansberry
>
> One can create a capability whose dynamic name is not resolved using the value of the last element of a path address (e.g. using the value of a parent resource). In this case, the logic for generating the dynamic name need to be modified in multiple places.
> # CapabilityReferenceRecorder.DefaultCapabilityReferenceRecorder.getDynamicDependentName(...)
> # AbstractAddStepHandler.recordCapabilitiesAndRequirements(...)
> # AbstractRemoveStepHandler.recordCapabilitiesAndRequirements(...)
> For reference, the clustering subsystems handle this via custom abstraction:
> https://github.com/wildfly/wildfly/blob/master/clustering/common/src/main/java/org/jboss/as/clustering/controller/Capability.java
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jboss-jira
mailing list