]> Contents Join Manager Jini 1.0 JoinManager Getting information from JoinManager Summary Finding a lookup service involves a common series of steps. Subequent interaction with them also involves common steps. A join manager encapulates these into one convenience class for services. A service needs to locate lookup services and register the service with them. Locating services can be done using the utility classes of ``Discovery Management''. As each lookup service is discovered, it then needs to be registered, and the lease maintained. The class JoinManager performs all of these tasks. There are two constructors public class JoinManager { public JoinManager(Object obj, Entry[] attrSets, ServiceIDListener callback, DiscoveryManagement discoverMgr, LeaseRenewalManager leaseMgr) throws IOException; public JoinManager(Object obj, Entry[] attrSets, ServiceID serviceID, DiscoveryManagement discoverMgr, LeaseRenewalManager leaseMgr) throws IOException; public JoinManager(Object obj, Entry[] attrSets, ServiceIDListener callback, DiscoveryManagement discoverMgr, LeaseRenewalManager leaseMgr, Configuration config) throws IOException, ConfigurationException; public JoinManager(Object obj, Entry[] attrSets, ServiceID serviceID, DiscoveryManagement discoverMgr, LeaseRenewalManager leaseMgr, Configuration config) throws IOException, ConfigurationException; } The first of these is when the service is new and does not have a service id. A ServiceIDListener can be added which can note and save the id. The second form is used when the service already has an id. The other parameters are for the service and its entry attributes, a DiscoveryManagement object to set groups and unicast locators (typically this will be done using a LookupDiscoveryManager) and a lease renewal manager. The third and fourth constructors add a Configuration parameter to the first and second constructors respectively. The following example uses the first constructor to register a FileClassifierImpl. There is no need for a DiscoveryListener, since the join manager adds itself as a listener and handles the registration with the lookup service. Note that a proxy has to be created using an Exporter, and then the proxy is passed as the first parameter to the JoinManager. An Ant build, deploy and run file for this is joinmgr.FileClassifierServer.xml There are a number of other methods in JoinManager, which allow one to modify the state of a service registration. A JoinManager can be used by a server to simplify many of the aspects of locating lookup services, registering one or more services and renewing leases for them. ©right;