A good way of finding this out is from the javadocs page of the Serializable interface, by switching from the Class view to the Use view (at the top of the page, select the "Use" option).
I believe that the title of this post is misleading. If the book you bought is not from Whizlab, then you have the author of the book to blame because he only provided two activations with the CD. But again, I doubt that the author did not specify this somewhere.
Tomasz, I took the ePractice exam for the 1.5 version and found no errors as far as I remember.
Doug, indeed in my case too there were many drag-and-drop questions, and also questions where you had to push a button to see the code. The ePractice exam did not come with any drag-and-drop questions, but I believe this is mentioned somewhere in there.
I passed the SCJP 5 exam today with 84%. I wrote about my experience since I started studying for the exam in my blog and thought I would share it with anybody interested here.
Good luck for those preparing for the exam and congratulations for those who passed it!
I believe the code is from K&B' book or Master Exam. As for your question, is the instance variable m1 of m2 ever (non-default) initialized? Look at the constructor being called when a new Mixer object is created and assigned to the m2 reference variable.
This is because when calling the go() method, you are passing a copy of the reference variable c2, not the c2 reference variable itself, nor the object that c2 points to. This is why the object that c2 refers to is not yet ready to be garbage collected. Furthermore, in the go() method you are not creating any new object, so c3 never actually pointed to an object. Basically, c1 (together with the Short object) would be GC.
To be honest, I expected this code to give you an ArrayIndexOutOfBounds exception due to the fact that at some point you will have "arr[5] = 0". Are you sure this is the right code for the answer you provided?
As Sagar mentioned, the problem is that in the BLBeck constructor, an implicit call to super is being made, but since the super constructor Vict() is not visible, to avoid a compilation error, you must either make it visible by changing its access control level to default, protected or coderanch, OR by explicitly invoking another constructor.
). I forgot about the -128 to 127 range for Short and Integer.