[jboss-jira] [JBoss JIRA] (AS7-4674) Child resources displayed out of order

[Thomas Diesler (JIRA)]

Thomas Diesler created AS7-4674:
-----------------------------------

             Summary: Child resources displayed out of order
                 Key: AS7-4674
                 URL: https://issues.jboss.org/browse/AS7-4674
             Project: Application Server 7
          Issue Type: Bug
          Components: Server
    Affects Versions: 7.1.1.Final
            Reporter: Thomas Diesler
            Assignee: Jason Greene
             Fix For: 7.2.0.Alpha1


A runtime resource may have child resource entries that have a natural ordering. Ordering should not be ignored

{code}
[standalone at localhost:9999 /] /subsystem=osgi:read-resource(include-runtime=true,recursive=true)
{
    "outcome" => "success",
    "result" => {
        "activation" => "eager",
        "startlevel" => 1,
        "bundle" => {
            "1" => {
                "id" => 1L,
                "location" => "org.osgi.enterprise",
                "startlevel" => 1,
                "state" => "RESOLVED",
                "symbolic-name" => "osgi.enterprise",
                "type" => "bundle",
                "version" => "4.2.0.201003190513"
            },
            "0" => {
                "id" => 0L,
                "location" => "System Bundle",
                "startlevel" => 0,
                "state" => "ACTIVE",
                "symbolic-name" => "system.bundle",
                "type" => "bundle",
                "version" => "0.0.0"
            },
            "6" => {
                "id" => 6L,
                "location" => "org.jboss.as.osgi.configadmin",
                "startlevel" => 1,
                "state" => "ACTIVE",
                "symbolic-name" => "jboss-as-osgi-configadmin",
                "type" => "bundle",
                "version" => "7.1.2.Final-SNAPSHOT"
            },
            "5" => {
                "id" => 5L,
                "location" => "org.apache.felix.configadmin",
                "startlevel" => 1,
                "state" => "ACTIVE",
                "symbolic-name" => "org.apache.felix.configadmin",
                "type" => "bundle",
                "version" => "1.2.8"
            },
            "4" => {
                "id" => 4L,
                "location" => "org.jboss.osgi.logging",
                "startlevel" => 1,
                "state" => "ACTIVE",
                "symbolic-name" => "jboss-osgi-logging",
                "type" => "bundle",
                "version" => "1.0.0"
            },
            "3" => {
                "id" => 3L,
                "location" => "org.apache.felix.log",
                "startlevel" => 1,
                "state" => "ACTIVE",
                "symbolic-name" => "org.apache.felix.log",
                "type" => "bundle",
                "version" => "1.0.0"
            },
            "2" => {
                "id" => 2L,
                "location" => "javax.servlet.api:v25",
                "startlevel" => 1,
                "state" => "RESOLVED",
                "symbolic-name" => "javax.servlet.api",
                "type" => "bundle",
                "version" => "2.5.0.Final"
            }
        },
        "capability" => {
            "javax.transaction.api" => {},
            "org.jboss.osgi.logging" => {"startlevel" => "1"},
            "javax.servlet.api:v25" => {},
            "org.jboss.as.osgi.configadmin" => {"startlevel" => "1"},
            "org.apache.felix.log" => {"startlevel" => "1"},
            "org.apache.felix.configadmin" => {"startlevel" => "1"}
        },
        "property" => {"org.osgi.framework.startlevel.beginning" => {"value" => "1"}}
    }
}
{code}

In the case of OSGi, the runtime bundles should be sorted by id.

For natural ordering, the ResourceEntry could implement Comparable<ResourceEntry> 
{code}
Set<ResourceEntry> getChildren(String childType)
{code}

alternatively, the controller could preserve the implicit order of the returned set (i.e. internally using a List). 



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira