Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-3751

DefaultCapabilityReferenceRecorder generates wrong dependent name if corresponding RuntimeCapability uses a dynamic name mapper

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 6.0.0.Alpha2
    • 5.0.0.Alpha2
    • Management
    • None

      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.

              pferraro@redhat.com Paul Ferraro
              pferraro@redhat.com Paul Ferraro
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: