org.springframework.util Documentation Differences

This file contains all the changes in documentation in the package org.springframework.util as colored differences. Deletions are shown like this, and additions are shown like this.

If no deletions or additions are shown in an entry, the HTML tags will be what has changed. The new HTML tags are shown in the differences. If no documentation existed, and then some was added in a later version, this change is noted in the appropriate class pages of differences, but the change is not shown on this page. Only changes in existing text are shown here. Similarly, documentation which was inherited from another class or interface is not shown here.

Note that an HTML error in the new documentation may cause the display of other documentation changes to be presented incorrectly. For instance, failure to close a <code> tag will cause all subsequent paragraphs to be displayed differently.

A ConcurrentHashMap that uses soft or ReferenceType#WEAK weak references for both {@code keys} and {@code values}.

This class can be used as an alternative to {@code Collections.synchronizedMap(new WeakHashMap>())} in order to support better performance when accessed concurrently. This implementation follows the same design constraints as ConcurrentHashMap with the exception that {@code null} values and {@code null} keys are supported.

NOTE: The use of references means that there is no guarantee that items placed into the map will be subsequently available. The garbage collector may discard references at any time, so it may appear that aan unknown thread is silently removing entries.

If not explicitly specified this implementation will use SoftReference soft entry references. @param The key type @param The value type @author Phillip Webb @since 3.2

A reference to an Entry contained in the map. Implementations are usually wrappers around specific javaJava reference implementations (ege.g., SoftReference).

The types of restructurerestructuring that can be performed.

Create a new {@code ConcurrentReferenceHashMap} instance.

Create a new {@code ConcurrentReferenceHashMap} instance. @param initialCapacity the initial capacity of the map

Create a new {@code ConcurrentReferenceHashMap} instance. @param initialCapacity the initial capacity of the map @param loadFactor the load factor. When the average number of references per table exceeds this value resize will be attempted

Create a new {@code ConcurrentReferenceHashMap} instance. @param initialCapacity the initial capacity of the map @param loadFactor the load factor. When the average number of references per table exceeds this value resize will be attempted @param concurrencyLevel the expected number of threads that will concurrently write to the map

Create a new {@code ConcurrentReferenceHashMap} instance. @param initialCapacity the initial capacity of the map @param loadFactor the load factor. When the average number of references per table exceeds this value resize will be attempted @param concurrencyLevel the expected number of threads that will concurrently write to the map @param referenceType the reference type used for entries

Create a new {@code ConcurrentReferenceHashMap} instance. @param initialCapacity the initial capacity of the map @param concurrencyLevel the expected number of threads that will concurrently write to the map

Calculate a shift value that can be used to create a power-of-two value between the specified maximum and minimum values. @param minimuxmValueminimumValue the minimum value @param maximumValue the maximum value @return the calculated shift (use {@code 1 < shift} to obtain a value)

A strategy for handling errors. This is especially useful for handling errors that occur during asynchronous execution of tasks that have been submitted to a TaskScheduler. In such cases, it may not be possible to throw the error to the original caller. @author Mark Fisher @since 3.0.

Handle the given error, possibly rethrowing it as a fatal exception.