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

CapabilityRegistryResourceDefinition provides inconsistent ordering of output

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 2.0.0.Beta6
    • Fix Version/s: 2.0.0.Beta7
    • Component/s: Management
    • Labels:
      None

      Description

      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.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                brian.stansberry Brian Stansberry
                Reporter:
                brian.stansberry Brian Stansberry
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: