# Reggie
v2.0_002 Release Notes

### Description

"Reggie" is the name of the contributed Jini(TM) lookup service implementation from Sun Microsystems. The specification for the Jini lookup service is available in html.

The specification for Reggie is defined not only by the Lookup Service section of the Jini Technology Core Platform Specification, but also by the API documentation (generated by the Javadoc(TM) tool) for `Administrable`.

### Changes since the v1.2.X release

Non-Activatable Persistent and Transient Implementations
  Reggie can now be run in three different modes:
  - Transient (and non-activatable)
  - Persistent and non-activatable
  - Persistent and activatable
  For examples of running Reggie in these different modes, see the `com.sun.jini.reggie` package documentation.

Modifications to Proxies
  Reggie's `ServiceRegistrar`, `ServiceRegistration`, `Lease`, and admin proxies now additionally implement the `ReferentUuid` interface, as well as the `RemoteMethodControl` interface if the underlying server remote reference implements `RemoteMethodControl`. `ServiceRegistrar` and admin proxies are now `equals` to one another if they are associated with the same service, regardless of changes to the proxy class or underlying server remote reference; resource proxies (such as leases and service registrations) are `equals` to other proxies for the same resource.

Configuration
  Reggie can now be configured using the `com.sun.jini.reggie` `Configuration` component. Configurable aspects include the exporter that Reggie uses to export its server back end, the proxy preparers that it uses to prepare received proxies, and the constraints that it applies during the discovery process. A full list of supported configuration entries is given in the `com.sun.jini.reggie` package documentation.

Logging
  Reggie now logs diagnostic information to the `Logger` named `com.sun.jini.reggie`. A list of logged events is given in the `com.sun.jini.reggie` package documentation.

System Properties
  The system properties listed below have been replaced by configuration entries for the `com.sun.jini.reggie` component, and are no longer supported:

  Property Name (no longer consulted) | Configuration Entry Name
  --- | ---
  `java.rmi.server.hostname` | `unicastDiscoveryHost`
  `net.jini.discovery.announce` | `multicastAnnouncementInterval`
  `net.jini.discovery.interface` | `multicastInterfaces`

  Note that the `java.rmi.server.hostname` system property may still be used by the RMI implementation used to export Reggie's server back end.

  Also, a new system property, `com.sun.jini.reggie.enableImplToStubReplacement`, is now supported. This system property has been added because JRMP impl-to-stub replacement no longer occurs by default for service proxies registered with Reggie. For the compatibility implications of the removal of JRMP impl-to-stub replacement, see the Compatibility with v1.2.1 page.

Removal of `com.sun.jini.reggie.RegistrarAdmin`
  The various administrative methods of the `RegistrarAdmin` interface have been replaced by equivalent configuration entries, and the `RegistrarAdmin` interface itself has been removed. Note that Reggie's admin proxy (returned from the `getAdmin` method of Reggie's main proxy) still implements the `DiscoveryAdmin`, `JoinAdmin`, and `DestroyAdmin` interfaces. A mapping of `RegistrarAdmin` methods to corresponding configuration entries for the `com.sun.jini.reggie` component is given below:

  `RegistrarAdmin` Method Name | Configuration Entry Name
  --- | ---
  `setLogToSnapshotThreshold` | `logToSnapshotThreshold`
  `setMinMaxEventLease` | `minMaxEventLease`
  `setMinMaxServiceLease` | `minMaxServiceLease`
  `setMinRenewalInterval` | `minRenewalInterval`
  `setSnapshotWeight` | `snapshotWeight`

  Note that the `logToSnapshotThreshold` and `snapshotWeight` configuration entries are only supported when running Reggie as a persistent service.

### Changes since the v2.0Beta release

Removal of JRMP Impl-to-Stub Replacement
  By default, Reggie no longer performs JRMP impl-to-stub replacement on service proxies passed to the `register` method of its proxy. This behavior can be re-enabled by setting the `com.sun.jini.reggie.enableImplToStubReplacement` system property to `true`.

Copyright 2004 Sun Microsystems, Inc. All Rights Reserved.