On Tue, Jan 11, 2011 at 11:53 AM, Simon Laws <[email protected]> wrote: > On Mon, Jan 10, 2011 at 9:03 PM, Johnny Simons <[email protected]> > wrote: >> In the beta1 release notes it says that remote domain support is disabled, >> whats the status of this? Does the trunk code have support for this now? >> >> J >> >> > > Hi Johnny > > The code is in trunk but it requires more work. > > The remote domain support relies on a distributed registry to share > domain information between nodes. We've had various implementations of > the registry including Hazelcast and Tribes. With the basic support we > have the idea is that you start a Tuscany node, telling it which > domain it belongs to, and it publishes information about the > components/services that it's starting. The intention is to separate > the registry from the way it's populated so, for example, you can > imagine it being populated using a centralized manager like we have in > the 1.x code base. That's not been ported across yet and currently > nodes populate it independently. > > Ant may have a better handle on what the status is as I forget what > the issue was in Beta1. We'll have to fire up the test cases and see > what works and what doesn't. I'll give it a go when I get the thing > I'm working on at the moment out of the way. >
The short answer is that it doesn't work properly yet/anymore. OTTOMH these are some of the things that need completing: - clean up APIs for creating and configuring distributed nodes - fix up at least one of the distributed registries, i think the Hazelcast one is closest of the existing ones to being usable but it has some limitations and it would also be good to have a more simple non p2p based registry - fix up the SCA client impl, that did used to work but the tests got taken out and now i think some of the function has been broken - fix the service URI's to take account of the domain so services in separate domains don't overwrite each other - support sca wire retargeting so when wire's get deployed / undeployed reference targets get updated - support distributed exports and policy so when resources are exported on one node those resources are available for import on other distributed nodes and probably other things i'm not remembering. It shouldn't be so hard to get the basic function going again but some of those will take a bit more work. Any chance you'd like to help get some of those things done? :) ...ant
