[jboss-jira] [JBoss JIRA] (WFCORE-1058) Encapsulate logic to specify dynamic capability name resolution from a PathAddress

[Tomaz Cerar (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13380503#comment-13380503 ] 

Tomaz Cerar edited comment on WFCORE-1058 at 3/17/17 8:09 PM:
--------------------------------------------------------------

This is now done as part of work on WFCORE-2202
On RuntimeCapabilty you now have #setDynamicNameMapper(Function<PathAddress,String[]>)
Which defines the mapping between path address and dynamic parts
There is also new CompositeAttributeDependencyRecorder which takes this dynamic parts into account where recording requirements.
When building attributes you have new variants to set capability reference
#setCapabilityReference(String referencedCapability, AttributeDefinition ... dependantAttributes)
and few others.


was (Author: ctomc):
This is now done as part of work on WFCORE-2202
On RuntimeCapabilty you now have #setDynamicNameMapper(Function<PathAddress,String[]>)
Which species the mapping between path address and dynamic parts
There is also new CompositeAttributeDependencyRecorder which takes this dynamic parts into account where recording requirements.
When building attributes you have new variants to set capability reference
#setCapabilityReference(String referencedCapability, AttributeDefinition ... dependantAttributes)
and few others.

> 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: Tomaz Cerar
>
> 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 a 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
(v7.2.3#72005)