Home/ Questions/Q 6574991
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T15:19:56+00:00

We do have a cache ( Map ) with objects of Class TestClass .

  • 0

We do have a cache (Map) with objects of Class TestClass. Another classloader initializes/loads TestClass at runtime again, so below code will threw a ClassCastException:

TestClass obj1 = (TestClass)map.get("key"); // throws a ClassCastException

ClassCastException when casting to the same class

Alright, I do understand this issue up to this point.

So, I was trying to find background information why is TestClass.class not equals TestClass.class. I assume that the different classloader set a different id to the ReferenceType? Anyone able to explain the background to me?

Best page I’ve found:
http://www.objectsource.com/j2eechapters/Ch21-ClassLoaders_and_J2EE.htm

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Yes, your research points to the right direction: the same class definition loaded by different class loaders is seen as two distinct classes by the JVM. Thus casting between them fails with ClassCastException.

    I think the difference is simply because there are two distinct class token objects in play. It has to be like this, since the classes loaded by the different loaders may in fact be different versions of the same class. It is known that the class token for every class is unique (within the same classloader realm, that is). It would open up a can of worms if the JVM started to compare class tokens by their various attributes, rather than by physical equality (==).

    • 0