WeakHashMap
. However, you can also specify hard keys and weak values, or any other combination. The default constructor uses hard keys and soft values, providing a memory-sensitive cache. This map is similar to ReferenceIdentityMap. It differs in that keys and values in this class are compared using equals()
.
This {@link java.util.Map Map} implementation does not allow null elements.Attempting to add a null key or value to the map will raise a NullPointerException
.
This implementation is not synchronized. You can use {@link java.util.Collections#synchronizedMap} toprovide synchronized access to a ReferenceMap
. Remember that synchronization will not stop the garbage collecter removing entries.
All the available iterators can be reset back to the start by casting to ResettableIterator
and calling reset()
.
Note that ReferenceMap is not synchronized and is not thread-safe. If you wish to use this map from multiple threads concurrently, you must use appropriate synchronization. The simplest approach is to wrap this map using {@link java.util.Collections#synchronizedMap}. This class may throw exceptions when accessed by concurrent threads without synchronization.
NOTE: As from Commons Collections 3.1 this map extends AbstractReferenceMap
(previously it extended AbstractMap). As a result, the implementation is now extensible and provides a MapIterator
.
@see java.lang.ref.Reference
@since Commons Collections 3.0 (previously in main package v2.1)
@version $Revision$ $Date$
@author Paul Jack
@author Stephen Colebourne
WeakHashMap
. However, you can also specify hard keys and weak values, or any other combination. The default constructor uses hard keys and soft values, providing a memory-sensitive cache.The algorithms used are basically the same as those in {@link java.util.HashMap}. In particular, you can specify a load factor and capacity to suit your needs. All optional {@link Map} operations are supported.
However, this {@link Map} implementation does notallow null elements. Attempting to add a null key or or a null value to the map will raise a NullPointerException
.
As usual, this implementation is not synchronized. You can use {@link java.util.Collections#synchronizedMap} to provide synchronized access to a ReferenceMap
.
@see java.lang.ref.Reference
@deprecated Moved to map subpackage. Due to be removed in v4.0.
@since Commons Collections 2.1
@version $Revision: 1.22 $ $Date: 2004/02/18 01:15:42 $
@author Paul Jack
WeakHashMap
. However, you can also specify hard keys and weak values, or any other combination. The default constructor uses hard keys and soft values, providing a memory-sensitive cache. This map is similar to {@link org.apache.commons.collections.map.ReferenceIdentityMap ReferenceIdentityMap}. It differs in that keys and values in this class are compared using equals()
.
This {@link Map} implementation does not allow null elements.Attempting to add a null key or value to the map will raise a NullPointerException
.
This implementation is not synchronized. You can use {@link java.util.Collections#synchronizedMap} to provide synchronized access to a ReferenceMap
. Remember that synchronization will not stop the garbage collecter removing entries.
All the available iterators can be reset back to the start by casting to ResettableIterator
and calling reset()
.
NOTE: As from Commons Collections 3.1 this map extends AbstractReferenceMap
(previously it extended AbstractMap). As a result, the implementation is now extensible and provides a MapIterator
.
@see java.lang.ref.Reference
@since Commons Collections 3.0 (previously in main package v2.1)
@version $Revision: 1.13 $ $Date: 2004/04/27 21:35:23 $
@author Paul Jack
@author Stephen Colebourne
WeakHashMap
. However, you can also specify hard keys and weak values, or any other combination. The default constructor uses hard keys and soft values, providing a memory-sensitive cache.The algorithms used are basically the same as those in {@link java.util.HashMap}. In particular, you can specify a load factor and capacity to suit your needs. All optional {@link java.util.Map} operations aresupported.
However, this {@link java.util.Map} implementation does notallow null elements. Attempting to add a null key or or a null value to the map will raise a NullPointerException
.
As usual, this implementation is not synchronized. You can use {@link java.util.Collections#synchronizedMap} toprovide synchronized access to a ReferenceMap
.
@deprecated use {@link org.apache.commons.collections.map.ReferenceIdentityMap} instead.
@author Andy Malakov
@version $Id: ReferenceMap.java,v 1.6.2.2 2005/12/21 22:27:47 tomdz Exp $
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|