upto me its very helpful to see the source code for understanding the things well.how the generics are implemented in collections.what are the method signatures for crucial methods.what are the exceptions thrown by a particular method.what are the interfaces particular classes implementing....wow! how many i can say.finally to do R&D on java?
thanks and regards<br />Santhi Bharath<br />SCJP 5.0, SCWCD 5.0
That's a good approach, and I'd suggest also that you study the API "as is". By that I mean study the API WITHOUT diving into the code - the guys who wrote the API have deep understanding of how to create good OO design. Part of the reason that the SCJP exam team put API topics in the exam is to give candidates an opportunity to study how the API is designed. In many cases you can view the design of the API itself as an example of good OO design principles. (Okay, I'm sure you can all find examples of bad design in the API - let's not go there :roll: ).
The reason I bring this up is because it kind of seems like the original question in this thread could be viewed as an attempt to somehow subvert the design intent of the language - in the end that will rarely be a good approach.
Spot false dilemmas now, ask me how!
(If you're not on the edge, you're taking up too much room.)