DefaultCapabilityReferenceRecorder generates wrong dependent name if corresponding RuntimeCapability uses a dynamic name mapper ------------------------------------------------------------------------------------------------------------------------------- Key: WFCORE-3751 URL: https://issues.jboss.org/browse/WFCORE-3751 Project: WildFly Core Issue Type: Bug Components: Domain Management Affects Versions: 5.0.0.Alpha2 Reporter: Paul Ferraro Assignee: Brian Stansberry CapabilityReferenceRecorder.DefaultCapabilityReferenceRecorder should be generalized to handle capabilities that use a dynamic name mapper. While most users can workaround the problem by using ContextDependencyRecorder instead - this is limited to resources that define a single capability.