On Tue, Jun 14, 2011 at 11:17 AM, Simon Laws <[email protected]> wrote:
>>>
>>> +1 although, if we're not going with sub-directories, I would add a
>>> convention something like.
>>>
>>> nameofnode-node.xml
>>>
>>> or similar to cover the shared file system case.
>>>
>>
>> I'm not sure i understand what you mean with that, could you explain
>> again or add a test showing what you mean?
>>
>> ..ant
>>
>
> Reading between the lines I think that multiple nodes will be started
> over a given domain directory and, I know this is putting words in
> your mouth but, I think that you think that only one node will be
> started over a particular domain directory.
>
> I'm taking into account the scenario where the directory (the domain)
> is visible from multiple machines and hence I want to start multiple
> nodes (one on each machine) each loading the contributions but running
> different composites. To get that to work I need to be able to
> distinguish one node configuration from another hence I suggest
> putting the node name in the name of the configuration file.
>
> Does that help?
>
Yes i'm thinking that a domain directory is for one node, so that would be:
/some/path/to/a/directory/domain1/
node.xml
/some/path/to/a/directory/domain2/
node.xml
and used with:
node1 = TuscanyRuntime.createNode(new
File("/some/path/to/a/directory/domain1"));
node2 = TuscanyRuntime.createNode(new
File("/some/path/to/a/directory/domain2"));
As opposed to:
/some/path/to/a/directory/
domain1.node.xml
domain2.node.xml
but that also works and is useable with:
node1 = TuscanyRuntime.createNode(new
File("/some/path/to/a/directory/domain1.node.xml"));
node2 = TuscanyRuntime.createNode(new
File("/some/path/to/a/directory/domain2.node.xml"));
Does that do what you want?
...ant
