# Mercury
v2.0_002 Release Notes

### Description

"Mercury" is the name of the contributed Jini(TM) event mailbox service implementation from Sun Microsystems. The Jini(TM) Event Mailbox Specification is available in html.

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

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

Modifications to Proxies
  Mercury's proxies now implement `RemoteMethodControl` if the underlying server remote reference does. Mercury proxies are also now smart proxies that are equal if they are associated with the same service, regardless of changes to the proxy class or the underlying server remote reference.

Configuration
  Mercury can now be configured using the `com.sun.jini.mercury` `Configuration` component, including configuring proxy preparation, lookup attributes, and groups. A full list of supported configuration entries is given in the package documentation.

Logging
  Mercury now logs diagnostic information to various `Logger`s prefixed by `com.sun.jini.mercury`. This functionality replaces the use of the `com.sun.jini.mercury.debug` system property. A description of what information is logged at what logging levels is given in the package documentation.

Removal of `com.sun.jini.mercury.*` properties
  The following properties have been removed without any equivalent configuration entries:
  `com.sun.jini.mercury.eventsPerLog`
    Determined the maximum number of events to place into any single event log file. Default = 10.

  `com.sun.jini.mercury.streamPoolSize`
    Determined the maximum number of concurrent event log input/output streams in use at any one time. Default = 10.

Copyright 2004 Sun Microsystems, Inc. All Rights Reserved.