How about just "type" ?
I don't want "node". There really is such a thing as a "resource"
(which
has operations), and then there is the tree structure used to represent
the resource tree. In that context "node" is ambiguous.
On 3/18/11 6:53 AM, Heiko Braun wrote:
IMO the parameter 'child-types' is confusing:
[/] :read-children-names(child-type=host)
{
"outcome" => "success",
"result" => ["local"],
"compensating-operation" => undefined
}
does it make sense to turn it into something like 'item' ('element' or
'node' would do also) ?
in that case it would read:
[/] :read-children-names(item=host)
{
"outcome" => "success",
"result" => ["local"],
"compensating-operation" => undefined
}
Ike
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat