Skip to main content
Jump to: navigation, search

Difference between revisions of "Discovery and Distribution Listeners"

Line 1: Line 1:
ECF's implementation of RFC 119 has a listener service API, so that clients can monitor and respond to the activities of the implementation during service registration and service publication (on the service host), and service discovery and service lookup/proxy creation (on the service consumer).
+
ECF's implementation of RFC119 has a listener service API, so that clients can monitor and respond to the activities of the implementation during service registration and service publication (on the service host), and service discovery and service lookup/proxy creation (on the service consumer).
  
 
For all of the listener interfaces below, the way for clients to create listeners is to use the whiteboard pattern to
 
For all of the listener interfaces below, the way for clients to create listeners is to use the whiteboard pattern to
Line 6: Line 6:
 
# Register the instance as a service
 
# Register the instance as a service
  
When appropriate events occur (i.e. a RFC 119 remote service is registered), the ECF RFC 119 impl will find all registered IHostDistributionListener services and notify them by calling the appropriate event method.
+
When appropriate events occur (i.e. a RFC119 remote service is registered), the ECF RFC119 impl will find all registered IHostDistributionListener services and notify them by calling the appropriate event method.
  
 
For example, here is how one would create and register a IHostDistributionListener
 
For example, here is how one would create and register a IHostDistributionListener

Revision as of 16:39, 3 June 2009

ECF's implementation of RFC119 has a listener service API, so that clients can monitor and respond to the activities of the implementation during service registration and service publication (on the service host), and service discovery and service lookup/proxy creation (on the service consumer).

For all of the listener interfaces below, the way for clients to create listeners is to use the whiteboard pattern to

  1. Create an instance of the interface
  2. Register the instance as a service

When appropriate events occur (i.e. a RFC119 remote service is registered), the ECF RFC119 impl will find all registered IHostDistributionListener services and notify them by calling the appropriate event method.

For example, here is how one would create and register a IHostDistributionListener

// define class to implement IHostDistributionListener
public class MyHostDistributionListener implements IHostDistributionListener {
   public void registered(ServiceReference serviceReference,IRemoteServiceContainer remoteServiceContainer, IRemoteServiceRegistration remoteRegistration) {
      System.out.println("hostRegistered\n\tserviceReference="+serviceReference+"\n\tremoteServiceContainer="+remoteServiceContainer+"\n\tremoteRegistration="+remoteRegistration);
   }
 
   public void unregistered(ServiceReference serviceReference, IRemoteServiceRegistration remoteRegistration) {
      System.out.println("hostUnregistered\n\tserviceReference="+serviceReference+"\n\tremoteRegistration="+remoteRegistration);
   }
}
...
// register new instance of MyHostDistributionListener as OSGi service
bundleContext.registerService(IHostDistributionListener.class.getName(),new MyHostDistributionListener(),null);

When a remote service is registered, the 'registered' method will be called, and when a remote service is unregistered the 'unregistered' method will be called.

Service Host

On the service, host there are two listeners

Copyright © Eclipse Foundation, Inc. All Rights Reserved.