Jini(TM) Technology Core Platform (JCP) Release Notes

JiniTM Technology Core Platform (JCP) 1.0 Release Notes


The Jini Technology Core Platform (JCP) software distribution consists of the Jini technology specifications, the classes and interfaces defined in those specifications (the net.jini.core.* software), the API documentation from those classes and interfaces, release notes for those classes and interfaces, a glossary of terms used in the specifications, and references to the specific copyrights and licenses that protect each of the aforementioned components.

This document contains information on packaging changes since the DC release of this product and release notes for the JiniTM Transaction specification.

If you have comments on the JCP, you can send email to jini-comments@java.sun.com. If you would like to submit a bug against the JCP, please send it to jini-submit@java.sun.com. If you encounter problems that you would like help with, you can subscribe to the jini-users list by sending email to listserv@java.sun.com, with a message of "subscribe jini-users".


Packaging Changes Since DC

The JCP, as it was released as DC, has been split into two separate products. Those specifications and software that were viewed as being "core" to the Jini platform were kept in the JCP and the software packages were moved from the parent package, net.jini, to net.jini.core. Those specifications and software that were viewed as "extensions" to the Jini platform were rebundled as the JXP, but there was no change to the software package structure; all of the classes and interfaces in the JXP retain the parent package, net.jini. In addition, the JXP contains the net.jini.space package, which was not released as part of the DC version of the JCP.

Specifically, package changes to the software in the JCP were:

    net.jini.core.discovery.LookupLocator
    net.jini.core.entry.Entry 
    net.jini.core.entry.UnusableEntryException
    net.jini.core.event.*
    net.jini.core.lease.*
    net.jini.core.lookup.*	(except DiscoveryAdmin)
    net.jini.core.transaction.*
    net.jini.core.transaction.server.*

JiniTM Transaction Release Notes

Changes Since Beta

The Jini Transaction (net.jini.core.transaction.* and net.jini.core.transaction.server.* ) interfaces and APIs have changed since Beta. Functional changes mainly reflect how transaction managers that support nesting are represented. Methods that support nesting behavior were moved into separate classes: NestableTransactionManager, NestableTransaction, and NestableServerTransaction.

In addition, the meaning of the commit and abort methods, which do not take timeout parameters, has changed. From the caller's point of view, when these methods returned, it used to mean that "a commit/abort has happened and all participants have been notified." In the current release of the Jini Transaction Specification, when these methods return it means that "the commit/abort has happened." The transaction manager guarantees that it will abort or commit the changes and contact participants appropriately. In a distributed system, at a given point in time, participants may not be reachable. This semantic change prevents a client from blocking indefinitely while waiting for the commit/abort method to return.


Copyright © 1999
Sun Microsystems, Inc. All Rights Reserved.