On Mon, Jun 30, 2008 at 4:24 PM, Hinde Bouziane <[EMAIL PROTECTED]> wrote:
> > > > ---------- Forwarded message ---------- > From: Hinde Bouziane <[EMAIL PROTECTED]> > To: [email protected] > Date: Wed, 25 Jun 2008 19:08:21 +0200 > Subject: get a reference to a domain from a remote program > Hi all, > > In the context of a distributed application, I would like to find an > existing domain from a program to be able to use services provided by > components created in already launched nodes. > For more details: > 1) I use the DomainManagerLauncher interface to launch a domain. > 2) I use the node2-launcher module to launch nodes (in the same way as > done in calculator-distributed). Let's suppose that one node contains a > component A. > - Until now, I had no problem to starts nodes. > 3) Now, from a program (that as a role of a client) I try to use a service > provided by component A. For that, I want to find a reference to the domain > created in 1) to asks for the wanted service. > > I'm using the 1.2 distribution. I found the SCADomainFinder class that > offers the getSCADomain operation in the node-api. It seems that this > operation provides a way to find an existing domain, but seems also be not > completely implemented (a todo comment ). Is it the case? or is the usage > of this operation is not compatible with the usage of node2... modules? > Otherwise, is there another way to find and get the reference to the > domain? > > Thank you for your help. > Regards, > Hinde > > Hi Hinde The SCADomainFinder feature is being removed from our next release (1.3) as it's not compatible with the Node2 implementation. What you could do is create a composite containing a component that references component A, let's call is AReference. If you then start a Node2 Instance configured to load the composite containing AReference you can then use the SCAClient API on Node2 to get a reference to AReference and the domain will ensure that the AReference component is connected to the A component wherever that is running. A bit clunky but we haven't yet rebuilt the client API for the new domain implementation. Any thoughts about how we should do this are most welcome. Simon
