My concerns are behind the questions you trimmed :-). Answers to these
questions will help me understand your approach. I relist the questions
below.
1) What's the result of the discovery? A list of SCA nodes (for example,
node.composite that describes the node configuration)?
2) Do we have a "manager" that initiate the discovery and maintain the
membership dynamically?
3) Where are the SCA contributions from? Is this part of the discovery?
4) Which part is responsible to manage the SCA contributions and resolve
composites at the domain level? The input to a SCA node is a deployable
composite and a list of SCA contributions (contribution uri + location).
5) I cannot find samples/helloworld-distributed. Where is it?
6) Can you describe the steps in sequence for this approach? I would like to
see how the players interact in this dynamic fashion and what information is
produced from each interaction.
Thanks,
Raymond
From: ant elder
Sent: Thursday, September 11, 2008 1:14 AM
To: [email protected]
Subject: Re: A new JMS impl of binding.sca and "dynamic" SCA domains
On Wed, Sep 10, 2008 at 4:45 PM, Raymond Feng <[EMAIL PROTECTED]> wrote:
Hi,
I have some concerns here as it starts to mix a few conceptually
independent perspectives for a SCA domain.
Could you explain what you mean by that? I know this dynamic approach is a
different from the way distributed domains work in Tuscany today but the
approaches are complementary, i'd like to eventually end up with both ways
working together at the same time. And given the flexible and
non-prescriptive language of the way SCA domains are described in the SCA
specs i think this should be fine.
Not sure why you couldn't find the sample, its in the sca samples folder at:
https://svn.apache.org/repos/asf/tuscany/java/sca/samples/helloworld-distributed/
...ant
