ls was supposed to be only for node path. I was thinking about something
like 'describe' or something to get a detailed info about the current
node (or the node in the argument of describe).
There is potentially a lot of info, i.e. attributes, operation, etc. I
haven't thought that through yet.
On 04/08/2011 04:27 AM, Scott Stark wrote:
Ah, ok, perhaps not then, but an ls of a leaf defaulting to this
read-resource op would be nice. I'll create a feature request and Alexey
can do what he wants with it.
On 4/7/11 7:23 PM, Brian Stansberry wrote:
> I'll let Alexey comment on whether he envisioned ls as showing the
> attributes of a resource as opposed to just showing the structure of the
> resource tree.
>
> /socket-binding-group=standard-sockets:read-resource(recursive=true)
> will give you all the details.
>
> /socket-binding-group=standard-sockets/socket-binding=http:read-resource
>
> will give you a single one.
>
> On 4/7/11 8:42 PM, Scott Stark wrote:
>> When I go into the admin shell and navigate down to the socket-binding
>> in the standard-sockets, tab completion shows the available bindings,
>> but I am unable to ls any particular socket-binding. I would expect that
>> when I ls socket-binding-group=standard-sockets/socket-binding=http I
>> would see the attributes of the node. Is that correct? This is what I see:
>>
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev