Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-6861

:read-resource-description operation should consistently order attributes by alphabet

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Major
    • None
    • 7.1.0.DR7
    • Management, User Experience
    • None

    Description

      While :read-resource-description returns an ordered list of resources with their descriptions for most resources, some resources do not return result consistent with this (resources ordered by alphabet).

      Affected resources:

      • /subsystem=iiop-openjdk:read-resource-description() returns unordered list of resources and their descriptions, while /subsystem=iiop-openjdk:read-resource() returns ordered list

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-1985 :read-resource-description operation should consistently order attributes by alphabet

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is related to

          Feature Request - Feature requests from customers and/or users WFCORE-1935 Add :read-attribute-description operation

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Coding In Progress
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-4262 ":read-resource(recursive=true)" generates output with random order, could be ordered alphabetically by keys

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Activity

            People

              jondruse@redhat.com Jiri Ondrusek
              mjurc@redhat.com Michal Jurc
              Votes:
              2 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: