Link Details

Gets your brain going before the big I. Use it as a starter list and whenever you come across a bit of Java nuance, add a question.

The "masters" title had me expecting to see a few more things like:

* What is the purpose of the static modifier?

* How can you create a memory leak in a Java program?

* How can you create a deadlock between two Threads?

* Is it better, in general, to use notify() or notifyAll()?

* How can you ensure a Collection is thread safe? Any gotchas? (hint: Iterators)

* How can you buffer I/O streams/readers/writers?

* What is a ThreadLocal variable and when can/should it be used?

Oh well, I guess we could probably fill up about 15-20 pages if we kept going... I'd rather go eat lunch :)

>> An abstract class may contain code in method bodies, which is not allowed in an interface.

In fact you can place method definitions into interface if they are static.

I voted for the article, however (and I *greatly cringe*), I have seen non-technical Managers who could not spell Java pull a list like this off the internet and use it for the technical part of an interview - worse I have seen newbie Java hackers that couldn't answer these questions use the list for an interview that they were Java kings. Oh well .... :-)

Regards,
Tom Pridham

And where can I get some?

I do have to agree that the article isn't that great. Many of the questions are full of ambiguity and it's hard to tell what they're asking for. And many of the answers are pretty subjective.