Some points:
1) The element name is <node>. Using "uri" as the attribute name is
consistent with the standard SCA XML style, such as component/@uri,
binding/@uri.
2) @domain is the URI of the SCA domain. The domain URI is defined by SCA
assembly spec. It uniquely identifies an SCA domain. I'm OK to change it to
be domainURI.
3) @domainRegistry holds a URI that can be used to connect to the domain
registry. Our EndpointRegistry uses the domain URI and domain registry URI
to connect to the back store that holds the endpoint descriptions.
4) Having an XML representation of the node configuration is good. It can
serve as the canonical persistence format. Sure, the node configuration can
be derived from many options:
* arguments on the command line
* programmatically via the NodeConfiguration model APIs
* from a live URL to the domain manager
* from classpath discovery
* ...
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.
Thanks,
Raymond
--------------------------------------------------
From: "ant elder" <[email protected]>
Sent: Tuesday, December 08, 2009 5:57 AM
To: <[email protected]>
Subject: Re: [2.x] node configuration attributes
On Tue, Dec 8, 2009 at 1:19 PM, Simon Laws <[email protected]>
wrote:
The node configuration file starts as follows:
<node xmlns:sca="http://docs.oasis-open.org/ns/opencsa/sca/200903";
xmlns="http://tuscany.apache.org/xmlns/sca/1.1";
xmlns:tuscany="http://tuscany.apache.org/xmlns/sca/1.1";
uri="http://sample/nodes/TestNode1";
domain="http://domain1";
domainRegistry="tribes:default">
This seems a little confusing.
- why "uri" rather than nodeURI?
- why "domain" rather than "domainURI?
- what's the difference between domain and domainRegistry?
Theres a lot that still needs to be cleaned up in this area. I dont
think theres any longer a need for the node uri should to be surfaced
to users at all. When i added the registry uri the intention was the
domain name would be derived from that, so with "tribes:default" i'd
expected the domain name to be "default" and not need to be defined
elsewhere. It would also be good to make all this easier to use from
the APIs without needing to write an XML document.
...ant
