[jboss-jira] [JBoss JIRA] (WFLY-1846) 'ls' for a resource not containing children returns nothing.

[Kabir Khan (JIRA)]

Kabir Khan created WFLY-1846:
--------------------------------

             Summary: 'ls' for a resource not containing children returns nothing.
                 Key: WFLY-1846
                 URL: https://issues.jboss.org/browse/WFLY-1846
             Project: WildFly
          Issue Type: Feature Request
          Components: CLI
            Reporter: Kabir Khan
            Assignee: Alexey Loubyansky


If I execute this for a resource containing children, it works as expected and shows both attributes and children, e.g.:
{code}
[standalone at localhost:9990 /] cd socket-binding-group=standard-sockets
[standalone at localhost:9990 socket-binding-group=standard-sockets] ls
local-destination-outbound-socket-binding          socket-binding                                     name=standard-sockets                              
remote-destination-outbound-socket-binding         default-interface=public                           port-offset=${jboss.socket.binding.port-offset:0}  
{code}
Now if I go to something with no children, it does not return the attributes
{code}
[standalone at localhost:9990 socket-binding-group=standard-sockets] cd socket-binding=http 
[standalone at localhost:9990 socket-binding=http] ls
[standalone at localhost:9990 socket-binding=http] 
{code}
However :read-resource works fine
{code}
[standalone at localhost:9990 socket-binding=http] pwd
/socket-binding-group=standard-sockets/socket-binding=http
[standalone at localhost:9990 socket-binding=http] :read-resource
{
    "outcome" => "success",
    "result" => {
        "client-mappings" => undefined,
        "fixed-port" => false,
        "interface" => undefined,
        "multicast-address" => undefined,
        "multicast-port" => undefined,
        "name" => "http",
        "port" => expression "${jboss.http.port:8080}"
    }
}
{code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira