Ok, so if we provide this information as part of the management interface you could get the list of the available components/services and then use the domain API to turn these component/service names into service references and hence you can then call through to your predefined service interface on each component.
The management service is implemented as a component in it's own right in order that you can get to it from wherever your code happens to be running. So you follow the sequence of steps something like. Get the management interface from the domain Get the component/service information you need from the management interface. The information available is based on the same model of wired components that you have access to today. For each component/service that you want to invoke an operation on turn it into a service reference (domain.getServiceReference) Call an operation using the service reference. Simon On 10/30/07, Jason Clark <[EMAIL PROTECTED]> wrote: > > Thanks for the reply. Comments below. > > -Jason > > This e-mail and any files transmitted with it are intended solely for the > use of the individual or entity to whom they are addressed. If you have > received this e-mail in error please notify the sender immediately and > delete this e-mail from you system. This message may contain company > proprietary, sensitive information and is intended only for the individual > named. Its contents may be covered under the Trade Secret Act of various > jurisdictions. If you are not the named addressee you should not > disseminate, distribute or copy this e-mail. If you are not the intended > recipient you are notified that disclosing, copying, distributing or > taking > any action in reliance on the contents of this information is strictly > prohibited. > > -----Original Message----- > > From: Simon Laws [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, October 30, 2007 3:59 AM > > To: [email protected] > > Subject: Re: Getting distributed components. > > > > Hi Jason, > > > > Some comments below. > > > > Regards > > > > Simon > > > > On 10/30/07, Jason Clark <[EMAIL PROTECTED]> wrote: > > > > > > Here's my use case. > > > > > > > > > > > > All my services extend a basic service interface that has some > > management > > > methods in it like shutdown and methods for gathering metrics reports > to > > > see > > > various bits of information. > > > > > > > > > > > > Is there a way to request all the available services in the > distributed > > > domain? > > > > > > Not just at the moment but the intention is to extend it to include this > > information. > > > > I noticed in the embedded SCADomain, I can get the componentManager and > > > request the names of all the components which I can use to gather each > > of > > > the components by the given Service interface. > > > > > > > > > > > > But, the other SCADomain, the getComponentManager method is commented > > out. > > > > > > We have a new domain implementation in > > > > modules/domain > > domain-api > > domain-impl > > > > There is an API for controlling the domain > > There is a default management service interface that provide read only > > information about the domain. > > > > I imagine we will start to move away from the domain implementations in > > host-embedded when the new interfaces start the settle down. They > haven't > > settled down yet so nows the time to get anything you need in there. > > > > Currently I only need the embedded one, but in the future I will > probably > > > have to deal with the distributed domain. Are there plans for > > implementing > > > the capability for the distributed model? > > > > > > Absolutely. What do you need to see? For example, currently you can ask > > about the the domain itself and the contributions it holds. You can also > > ask > > about the nodes the domain has and find which contributions are running > on > > which node. It would be fairly straightforward to extend this to provide > > information about components. Is the list of component names in the > domain > > sufficient? > > What I would like to do is dynamically gather all the services available > by > a common interface and query them for information without having to know > there exact implementation or higher level interface. If it works just > like > the embedded domain where I can just request component names and get > services by the general interface, all would be well. > > > > > -Jason Clark > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
