Ranch Hand
+ Follow
since May 31, 2000
Merit badge: grant badges
For More
Cows and Likes
Total received
In last 30 days
Total given
Total received
Received in last 30 days
Total given
Given in last 30 days
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by rajsim

I too am looking for more information.
Vibha has listed some books in this post http://www.javaranch.com/ubb/Forum25/HTML/000022.html
Do you hava knowledge of any online resources that can be of help?
Everything posted here after 4:00 PM August 7 ...
has stuck to all the old threads, can it be removed?
Nobody will post new discussions in the old threads because
of the message. Also, people viewing old threads may get the
impression that the upgrade is still going on.
23 years ago
I agree with thomas.
In addition, class level lock could also be obtained by using ".class" as in
synchronized (test5.class) {
interestingly, you could also apply the ".class" to a primitive and use it like the following:
synchronized (int.class) {
beyond SCJP objectives, isn't it?
Hi Ravi,
Don't worry. You will surely clear it next time.
For benefit of those who haven't taken the test yet,
would you please share your results from various mock
exams taken before you took the certification test.
You could add :
unary + and - (operates on numeric primitives)
() (operates on ?expressions? )
[] (operates on array references)
(typecasting) (operates on references and primitives)
. (dot) (operates on references)
instanceof (operates on references)
and also ?: though it is debatable whether it is included in
the objectives. However it appears in many mocks.
Do not worry too much about sockets and concentrate on streams.
If you know streams well, you should be safe.
As inner class is being extended outside its enclosing class,
you have to pass a reference to the enclosing class in its
This concept is 99% out of scope of the SCJP test. Also, the
guide you are studying is covering many more such out of scope
e. is wrong. JVM usually exits only when all user threads finish.
d. multiple threads accessing a method will lead to producing junk
is ambiguous.
You can say that multiple threads accessing a method of the same object might produce junk (unpredictable results) if no proper synchronization is done
There is no error when I compiled it using JDK 1.3 and jikes!
For wrapper classes, if you compare objects of different types
using "equals", it will return false.
If you overload myMethod(Object) with myMethod(String) and call
with myMethod(null), compiler will consider myMethod(String) as
more specific and call it.
If you have myMethod(Integer) as well myMethod(String), they
are equally specific as both extend Object directly.

[This message has been edited by rajsim (edited August 07, 2000).]
If you prefer, you can try it out yourself here

[This message has been edited by rajsim (edited August 07, 2000).]
There is nothing wrong with the code, JDK 1.3 compiles it OK.