This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
As far as compilation is concerned, compiler doesn't know anything about 'new Super()' only JVM can know which object is being created. Compiler doesn't have any problem because you are downcasting 'something' to 'Sub' and assigning the value to 'Sub' reference which is perfectly acceptable for compiler but when it comes to JVM (at runtime) it complains that
"I can't downcast Super "object" (not reference) to another class (even to its subclass)."
downcasting in object reference is acceptable in following case:
//code Super superReference= new Sub(); Sub subReference=(Sub) superReference;
because here we are downcasting super class reference (which refer to sub class object) to sub class one.
Good explanation, Vaibhav. When you put an explicit cast Sub subObj=(Sub)new Super();, you are telling the compiler to ignore the type of the reference and that you are make the compiler believe that at runtime the reference will point to the correct object.
However, in your case, at runtime the reference is not pointing to an object of class Sub (or its subclass). So the JVM throws the exception.
Note: You can think of this statement: Sub subObj=(Sub)new Super(); as : Super tempReference = new Super(); Sub subObj=(Sub)tempReference;