Hi Jason, Welcome to Tuscany!

Comments below...

Would be great to have your input on how some of these features should work
. So keep asking the questions:-)

Regards

Simon

On 10/18/07, Jason Clark <[EMAIL PROTECTED]> wrote:
>
> Another question. Is there a way to load composites and components at
> runtime? I'm looking at issues of distributed application survivability
> and
> in the event that a given service is no longer functional (hardware crash,
> or other problems), I want to be able to relaunch a portion of the domain
> after the component crashed. Is that possible?


There is an api for loading composites. It you look at most of our samples
you see that they use a domain api  to read a composite file which has the
effect or loading the application. We are doing some work on the node and
domain apis now so they have moved on a little from the 1.0 release. The
idea with the distributed domain is that you can have mulitple nodes in a
domain. A node is something that will run SCA applications, i.e. read and
run an SCA contribution. The nodes register with the domain and when the
nodes expose services they register those with the domain also. With this
information you can build SCA applications without having to explicitly
specify endpoints as  long as you are connecting components within the
domain.

If a node crashes you can just restart is again and it will re-register.
There is a bit of code commented out in the invoker for the default binding
that does retries and looks up the endpoint again in the case that the
endpoint can't be reached, i.e. the target node has failed. There was some
issue with it so that needs looking at but if we fix that then basic
restarts should be ok.


The best example I could find in the samples in the calculator-distrubuted
> example in the 1.0-incubating release, but the readme file lists a few
> resource directories that are not in the project (resource/domain,
> resource/management). Is the readme incorrect or are the files really
> missing?


Yeah, that looks like a mistake in the documentation. Can you raise a JIRA
for that and I'll fix it. The connection between the domains and the nodes
within it is actually implemented as an SCA application. That's what the
domain and management directories had in them. These have been moved now and
are currently node-impl/src/main/resources/node.composite and
domain-impl/src/main/resources/domain.composite which seemed to make more
sense.

Thanks.
>
>
>
>
>

Reply via email to