net.jini.entry package
Apache River v3.0.1 Release Notes

Description

Changes since the v2.2.0 release

None

Changes since the v2.1.1 release

None

Changes since the v2.0.1 release

The API Documentation is Now the Formal Specification

Previously, the formal specification for the net.jini.entry package was a separate document. With this release, the formal specification is the revised API Documentation. As part of this change the specification language was generally cleaned up and made tighter.

Behavior of Various AbstractEntry Methods Clarified

The previous versions of the specification for net.jini.entry.AbstractEntry did not specify how the static equals, hashCode, and toString methods behaved if passed null values. This version of the specification specifies that :

• equals should return true if both arguments are null, and false if only one argument is null.
• hashCode should return 0 if passed null.
• toString should return "null" if passed null.

Note: Previously our implementation of AbstractEntry would throw a NullPointerException if any of these methods were passed a null value.

Also, the specification of the static toString method was changed to require that the returned string include the name of the argument's class.

UnusableEntriesException Added

The net.jini.entry.UnusableEntriesException class was added. UnusableEntriesException can be used by methods that normally return a collection of entries when one or more of the entries can't be unmarshalled.

http://www.apache.org/licenses/LICENSE-2.0