[jboss-as7-dev] making child-type in read-children-names optional

Alexey Loubyansky alexey.loubyansky at redhat.com
Wed Feb 23 10:01:23 EST 2011


Actually, read-child-types seems like a better idea to me.

On 02/23/2011 03:46 PM, Brian Stansberry wrote:
> I agree that we need to make this easier; I hit a similar pain point
> playing with the CLI.
>
> I'm concerned about further blurring two different but blurry concepts
> though -- child resources (where a resource is a logical thing that has
> an address and exposes attributes and operations) vs a child of a DMR
> ModelNode.
>
> WDYT about having a separate operation read-child-types to get this
> information?
>
> On 2/23/11 8:16 AM, Alexey Loubyansky wrote:
>> The intent is to read children names of the current node/address. With
>> child-type required it complicates things (the most difficult would be
>> to get a list of root node names since there is no common type for them).
>>
>> So, can we make child-type optional? In the mean time, I've made it in
>> the cli branch
>> https://github.com/aloubyansky/jboss-as/commit/f0b3149fcd744b6968bd72162cf2e947765ea0a4
>>
>> Thanks,
>> Alexey
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
>



More information about the jboss-as7-dev mailing list