Java Developers Almanac 1.4 Vol. 1
What's the Book About?
The Almanac is divided into four main parts: packages, which covers every package in the core Java distribution, with the exceptions of the AWT, Swing, and printing; classes, which lists every class in alphabetical order, including all of its methods and fields; topics, which details the changes between each version of Java; and cross-reference, which allows you to look up every class, interface, and member type in Java 1.4.
Section 1, the package list, gives you every package in Java 1.4, every class inside those packages, the top-level description of the classes (from Sun's JavaDoc), a note of what JDK version the class was born in, an abstract/final indicator, and a hierarchy of the classes in the package. If this were all, it might be a nice, basic Java reference.
In addition to the strict listing, however, are hundreds of examples of how to use the classes; some basic, some obvious, and some you probably haven't seen.
The examples are extremely handy, if only to point out various utilities included with Java that you might otherwise not know about. With over 500 examples in the book, there's probably one you haven't seen or want to understand better.
There's also a website with all the code available at javaalmanac.com, so you don't have to type in every example you want to use in your code.
Section 2 provides a listing of every class in the covered packages in alphabetical order, along with all the signature of every public method in those classes. The book also cross-references every example in part 1 for each method. So, if you want to know how to better use ResultSet.afterLast(), you only need find the ResultSet class, and next to the afterLast() method are the two examples that use that method. With this easy organization, it's very straightforward to find any example you're looking for.
Part 3 goes through every major JDK release, starting at 1.0, and tells you everything you could possibly want to know about that release. You can find a statistical analysis of each release, including how many packages, classes, and members there are, how many classes in each package, new and removed classes and methods, deprecations, and all defined exceptions. I've certainly never seen a better or more compact reference on the differences between the JDKs.
Finally, part 4 gives a complete cross-reference for every class, interface and member mentioned. If you want to find every class that throws a ParseException, this is the place to find it.
What's Bad?The one bad thing that strikes me about this book is actually just a simple question: Why should I use it when most of this information is at my fingertips in an IDE? Sun's JavaDoc is nicely thorough, and includes most everything in this book, the examples being a notable exception. Parts 3 and 4, of course, are not at all included in the JavaDoc, but I'm not sure how often I might need those sections.
So What's In It For Me?If you're a down-and-dirty professional Java programmer, this book may very well be useful to you. The examples are quite handy, and as a reference to Java, it covers most anything you might need. Much of the information in the last two sections is hard to find in one coherent compilation. At $25 MSRP, it's an excellent value for all the information packed into the book.
Table of Contents- Preface
- Part 1: Packages
- Part 2: Classes
- Part 3: Topics
- Part 4: Cross-reference
You can purchase Java Developers' Almanac 1.4 Vol. 1 from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
Looked like a good book for beginners or those who don't want to view Javadocs over the 'net.
Unnecessary for anyone who's either comfortable with Javadocs or has done a moderate amount of OOP.
As was stated, you can get just about everything in this book online directly from Sun, for free.
4. Quit job, become crack addict bum on downtown street that other Java developers at an earlier stage than yourself stare at and don't give money to.
Was that you I walked by this morning?
Sounds like someone is a little envious of us successful, well paid, easy job, lots of spare time for OSS java developers who date lingerie models 2 at a time.
I don't have a sig...Do you??
Online references are all well and good if you already know exactly what you are looking for. However, a printed manual is ideal for browsing. I read them over on the subway rides. I'm not trying to memorize every class and method name, just learn what classes and methods are available.
I can then use online help to lookup the details later on. (The old "I know there's a class that does this...") Without the paper copy, it's far too likely that I'll only use classes that I have been made aware of in previous projects.
It's also why I find the absence of printed manuals for many programs very annoying. Why bother to add a feature to a product when most of your users will never learn that the feature exists!