You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Spring's CachedIntrospectionResults class traditionally comes with three different modes of static caching, primarily for defensiveness in terms of ClassLoader leaks. These three modes can be simplified to two: basically traditional ClassLoader layouts (with embedded Spring jars within the application) and non-traditional layouts (with the Spring jars higher up the hierarchy or in a different node of the ClassLoader tree altogether).
Previously, CachedIntrospectionResults had three modes of caching, with the intermediate mode relying on WeakReferences in the JDK PropertyDescriptor implementation. Since the JDK is actually using SoftReferences there these days, losing information in case of a GC run with tough memory constraints, we want to allow for hard references in PropertyDescriptor objects and therefore use a full WeakReference for the CachedIntrospectionResults object itself.
Juergen Hoeller opened SPR-10028 and commented
Spring's CachedIntrospectionResults class traditionally comes with three different modes of static caching, primarily for defensiveness in terms of ClassLoader leaks. These three modes can be simplified to two: basically traditional ClassLoader layouts (with embedded Spring jars within the application) and non-traditional layouts (with the Spring jars higher up the hierarchy or in a different node of the ClassLoader tree altogether).
Issue Links:
Referenced from: commits bed2134, 0ee1256, c368068, 4a8be69
The text was updated successfully, but these errors were encountered: