See my comments inline.
Thanks,
Raymond
--------------------------------------------------
From: "ant elder" <[email protected]>
Sent: Tuesday, December 08, 2009 2:58 PM
To: <[email protected]>
Subject: Re: [2.x] node configuration attributes
[[snip]]
What are the use cases for the XML representation? We dont actually
have anything in 2.x that needs this yet, could it be left till there
is something?
Yes, we do.
* We use the node.xml files to configure the client and server node in
itest-nodes-two-nodes-two-vms-test.
* We use it in web application integration so that a node can be created
from the webapp from a node.xml which can be local or remote.
* We plan to bring up the Domain Manager which will provision the domain
into a set of nodes. The configuration will be served using the node.xml
format.
4) I don't think node/@uri should be removed. Multiple nodes can have the
same domain URI and domain registry URI. The node URI should uniquely
identifies a node within an SCA domain. We can use a simple name instead
of
URI.
What are the use cases for the node URI? The "node" is a concept thats
not in any SCA spec which we're making up for Tuscany so I'm trying to
understand if there are real reasons for needing to expose a node uri
in any user API?
Node URI is used to uniquely identify a node within the SCA domain. It's
similar as the domain or contribution URI. You can view it as an "id" of the
node. If the URI is not provided, we will generate one. Having a
user-defined ID makes it simpler to manage the nodes (for example, in the
domain manager).
...ant
