On 8/16/07, Simon Laws <[EMAIL PROTECTED]> wrote: > > > > On 8/16/07, Giorgio Zoppi <[EMAIL PROTECTED]> wrote: > > > > Hi, > > i'm highly interested in contributing to the distributed runtime. > > Actually I'm trying to understand if this component model could be the > > building block for creating autonomic components. An autonomic > > component can consist of one or more managed components coupled with a > > single manager that controls them. To pursue its goal, the manager may > > trigger an adaptation of the managed components to react to a run-time > > change (i.e. fault, load balancing, etc). > > Some questions..i've updated the svn and it builds but not the > > distributed-calculator. > > Why? (It could be for me a starting point). > > Cheers, > > Jo. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > Hi Jo and welcome to Tuscany > > I'm just making some changes to the calculator sample to fix it up so it > will work again. What we have is a a simple scenario where you start 3 nodes > that run SCA components for different parts of the calculator application > and the nodes talk to a registry to find out what components are on which > node. Very simple at the moment but the framework is in place to add all > sorts of interesting component management options. Sounds like you have some > good ideas. Let me get the sample fixed up and I'll post back here. You can > then look at something that runs. > > Regards > > Simon > Hi Jo, I've just checked in the fixes and re-enbabled:
binding-sca-axis2 module which provides a remote version of the default binding between SCA components distributed-impl module which provides some abstractions of distributed domains and nodes and some interfaces for service registration and location calculator-distributed which, provides a simple sample of tuscany running distributed I get a clean build on windows so give it a try and let me know how you get on. The tests that run during the mvn build use an in memory registry so all the nodes run in one VM. This in memory version is replaced in the calculator distributed sample with a network version. You can make the sample go by starting four separate VMs using the ant build file provided: Run up the node that provides the registry ant runDomainNode Run up the node that runs the add service ant runNodeB Run up the node that runs the subtract service ant runNodeC Run up the node that runs the Calculator services and drives calls to the various methods ant runNodeA Regards Simon
