Questions about JDK-8136353 "ClassValue preventing class unloading"
William ML Leslie
william.leslie.ttg at gmail.com
Thu Jan 7 01:18:10 UTC 2016
On 7 January 2016 at 07:34, Peter Levart <peter.levart at gmail.com> wrote:
> ClassValue API could use a different strategy and reference the cached
> instance of type T from ClassValue<T> instance instead, but then you would
> have a problem with ClassValue instances reachable from other class loaders
> than the cached instances of type T.
>
> Regards, Peter
Is the problem with this strategy [together with a
java.util.WeakHashMap] that without this strong reference to the Class
object, the Class itself could be collected?
--
William Leslie
Notice:
Likely much of this email is, by the nature of copyright, covered
under copyright law. You absolutely MAY reproduce any part of it in
accordance with the copyright law of the nation you are reading this
in. Any attempt to DENY YOU THOSE RIGHTS would be illegal without
prior contractual agreement.
More information about the mlvm-dev
mailing list