[jboss-jira] [JBoss JIRA] (AS7-620) Support for ls of a leaf node in admin console equating to :read-resouce

Jason Greene (Updated) (JIRA) jira-events at lists.jboss.org
Thu Nov 3 16:54:45 EDT 2011


     [ https://issues.jboss.org/browse/AS7-620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Greene updated AS7-620:
-----------------------------

         Assignee: Alexey Loubyansky
    Fix Version/s: 7.1.0.CR1
         Priority: Minor  (was: Major)


What do you think about this Alexey?
                
> Support for ls of a leaf node in admin console equating to :read-resouce
> ------------------------------------------------------------------------
>
>                 Key: AS7-620
>                 URL: https://issues.jboss.org/browse/AS7-620
>             Project: Application Server 7
>          Issue Type: Feature Request
>          Components: CLI
>    Affects Versions: 7.0.0.Beta2
>            Reporter: Scott Stark
>            Assignee: Alexey Loubyansky
>            Priority: Minor
>             Fix For: 7.1.0.CR1
>
>
> I was taking the cli jboss-admin.sh tool for a test drive, and using ls and tab completion to navigate down to the socket-binding-group=standard-sockets/socket-binding=http leaf, and was expecting an ls or at least an ls -l to display the attributes. Brian noted this might be expected, so this request is to have the ls dump out the leaf attributes as though a :read-resource operation was performed on the node.
> [localhost:9999 /] ls
> extension               path                    subsystem
> deployment              management-interfaces   interface
> socket-binding-group
> [localhost:9999 /] ls socket-binding-group=standard-sockets/socket-binding=
> socket-binding=http
> socket-binding=https
> socket-binding=jmx-connector-registry
> socket-binding=jmx-connector-server
> socket-binding=jndi
> socket-binding=messaging
> socket-binding=messaging-throughput
> socket-binding=osgi-http
> socket-binding=remoting
> socket-binding=txn-recovery-environment
> socket-binding=txn-socket-process-id
> socket-binding=txn-status-manager
> [localhost:9999 /] ls socket-binding-group=standard-sockets/socket-binding=http
> [localhost:9999 /] ls -l socket-binding-group=standard-sockets/socket-binding=http
> [localhost:9999 /]
> [localhost:9999 /] /socket-binding-group=standard-sockets/socket-binding=http:read-resource
> {
>     "outcome" => "success",
>     "result" => {
>         "name" => "http",
>         "interface" => undefined,
>         "port" => 8080,
>         "fixed-port" => undefined,
>         "multicast-address" => undefined,
>         "multicast-port" => undefined
>     },
>     "compensating-operation" => undefined
> }

--
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

        


More information about the jboss-jira mailing list