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

CapabilityRegistryResourceDefinition provides inconsistent ordering of output

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 2.0.0.Beta7
    • 2.0.0.Beta6
    • Management
    • None

      The output from CapabilityRegistryResourceDefinition is inconsistently ordered. We want consistent output between reads.

      The RegistrationPoints are stored in CapabilityRegistration in a LinkedHashSet, but when they are provided to CapabilityRegistryResourceDefinition they get put in a plain HashSet.

      The capabilities themselves are not stored in any order, but when provided to CapabilityRegistryResourceDefinition they could be ordered.

              bstansbe@redhat.com Brian Stansberry
              bstansbe@redhat.com Brian Stansberry
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: