0% found this document useful (0 votes)
23 views6 pages15 Tricky Corejava Questions
The document discusses compareTo() methods, stateless and stateful beans, overriding static methods, blank final variables, and late binding.
Uploaded by
Ravi Chandra Reddy MuliCopyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
23 views6 pages15 Tricky Corejava Questions
The document discusses compareTo() methods, stateless and stateful beans, overriding static methods, blank final variables, and late binding.
Uploaded by
Ravi Chandra Reddy MuliCopyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
/ 6
You might also like
- 100% (1)Section 1 (Answer all questions in this section) 1. Why would a programmer use polymorphism rather than sticking to a standard array? Mark for Review (1) Points Because arrays only work using the same object type and polymorphism provides a way around this. (*) Because it is easier to add or remove objects using polymorphism even when all of the objects are of the same type. Because arrays are more complex and polymorphism simplifies them by restricting them to only contain the same type objects. A programmer wouldn't use polymorphism over a standard array. Correct Correct 2. If Sandal extends Shoe, it is possible to declare an object such that Sandal s = new Shoe(); Mark for Review (1) Points True False (*) Correct Correct 3. It is possible to override methods such as equals() and toString() in a subclass of Object to fit the needs of the objects of the subclass. True or false?3 pages
