Java Developers Almanac 1.4 Vol. 1

Jason Bennett writes "The Java Developer's Almanac is an interesting cross-breed of a book. On one hand, it's a reference book for the entire Java 1.4 API, complete with a listing for every method in every class in the API. On the other hand, it's a mini-tutorial, as it comes with myriad examples of how to use various Java classes. In the end, though, it's a book geared toward the advanced Java developer, especially one facing a new part of the API who needs a little guidance." Read on for his review. Java Developers Almanac 1.4 Vol. 1 author Patrick Chan pages 1007 publisher Addison Wesley rating 7/10 reviewer Jason Bennett ISBN 0201752808 summary A concise reference to every class and method in Java 1.4, with examples for many.

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

1. Preface
2. Part 1: Packages
3. Part 2: Classes
4. Part 3: Topics
5. 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.

Comments

Perfect

[jimmyCarter]

This is what I'm looking for when picking up a book to pick up a new language. Give me the class library API and some examples. For more advanced topics like multi-threading, I'm going to want something with maybe a little more depth and background on the topic.

Whenever I'm developing Java or C#, I spend most of my research time just browing the base class libraries anyway, so I can't think of a better toilet-time companion.

Thanks for the review.

Cheaper on Amazon

[ProlificSage]

Check it out here for $17.99 USD.

Re:Cheaper on Amazon

[RocketJeff]

If you're doing price comparisons for books, Best Book Buys can't be beat.

A search for The Java Developers Almanac v1.4 by ISBN shows that there are several shops (including my favorite, BookPool) with lower prices then Amazon.

A moment of clarity

[Anonymous Coward]

At first I thought to post a standard "I hate Java 'cos it's slow" flamebait, but as I was writing it I suddenly felt empty and tired as if trolling had become devoid of any meaning.

Then I realized what's wrong. I'm 31, I have a good secure job and I am financially well off. Yet, I am still a virgin, I've never even kissed a woman and I spend inordinate amounts of time on the web trolling Slashdot. Instead of this shit I could be chatting with my coworkers, making friends after work and actually having fun in the real world instead of downing a sixpack every evening alone at home and jerking off to some porn before I go to sleep.

Goddamn I'm depressed. Life is hell.

Re:A moment of clarity

[Anonymous Coward]

The holidays are hard on all of us.

"us" being the slashdot virgins.

Re:A moment of clarity

[hendridm]

> Imagine a geek with _very_ expensive hardware tastes, who can't get a job, and even gets turned down by Jack in the Box due to lack of experience, despite the fact I spent 4 years working a register.

Wow, you're preaching to the choire, brother. You have basically described me exactly. After graduating from college, I got turned down for all the good jobs of course, but I even got turned down for a job at Sears and Lowe's despite having a little over 3 years experience doing customer service and register and a local hardware store. Best Buy finally gave me a job, but they don't care much for my bachelor's degree and I don't think I fit the corporate culture very well...

On the bright side, I have a girlfriend whom I love very much and have been serious with for quite some time. Best of all, she's a geek too (I saw her once take a wireless-enabled laptop to the shitter, which is something I have not done yet).

One tiny almost pointless nitpick...

[sawilson]

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.

Maybe it's just me, but I force myself to type in
every example by hand from a book because I find
I have better comprehension of the material down
the road. But then again, I'm not "one who loves
code". I'm more of the writing code to automate
tasks type as apposed to a hardcore, sit in front
of your favorite editor for 8 hours straight making
elaborate things type person. Those guys are special
in a weird but positive way. A guy I used to work
with named Robert Sanders was the type that just
looked at code and "got it". Definitely not my
thang. He'd probably benefit from going to the
website for a cut and paste.

Re:One tiny almost pointless nitpick...

[sawilson]

Actually, Robert was the CTO at the time. He's famous for his part in creating dos emulation for
unix. You'd be lucky to hire him, assuming you
could afford him. I'm just lowly sawilson famous
for nothing that important.

Re:One tiny almost pointless nitpick...

[Enonu]

The Tao of Programming - Book 4, Section 4

Prince Wang's programmer was coding software. His fingers danced upon the keyboard. The program compiled without an error message, and the program ran like a gentle wind.

``Excellent!'' the Prince exclaimed, ``Your technique is faultless!''

``Technique?'' said the programmer turning from his terminal, ``What I follow is Tao - beyond all techniques! When I first began to program I would see before me the whole problem in one mass. After three years I no longer saw this mass. Instead, I used subroutines. But now I see nothing. My whole being exists in a formless void. My senses are idle. My spirit, free to work without plan, follows its own instinct. In short, my program writes itself. True, sometimes there are difficult problems. I see them coming, I slow down, I watch silently. Then I change a single line of code and the difficulties vanish like puffs of idle smoke. I then compile the program. I sit still and let the joy of the work fill my being. I close my eyes for a moment and then log off.''

Prince Wang said, ``Would that all of my programmers were as wise!''

Checked it out

[Rew190]

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.

Printed API references considered harmful

[Bemmu]

I have never understood printed API references. It's so much easier to be able to do a quick find on a computer. Reminds me of some Linux book that was just printed man pages. Yes I like reading real books rather than looking at a screen, but if I need to reference an API I'm already looking at the screen!

Re:Printed API references considered harmful

[west]

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!

Re:Printed API references considered harmful

[n3m6]

i found the exact opposite to be true. i learned php thru just the o'reilly pocket reference. its so much easier just to browse thru the functions and see what will suit where. and/or read it at some coffee shop just to learn what the language/library has to offer. since i know c++ i have to grasp on to java's API to learn it.. i think this book will do good for me..

Re:Java in 6 easy steps

[Vaulter]

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.

Printed APIs and Java 1.4 comments

[Hirofyre]

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?

I like having this sort of info in print, even though what you say is true, it is available from most IDEs. It is nice to be able to put a post-it note or write a reminder in some classes who's method signature are not too intuative.

Having been a java programmer for 3 or so years, I think Java 1.4 is a big step forward, and a lot of the newer packages are great additions (the logging package, for example). The flexability of that package alone makes Java a lot more robust and attractive.

Sounds better than...

[GeckoFood]

Java Complete, by Sybex. That book touts itself as a cheap book to learn Java and even has a good dump of the APIs at the end of the book. That said, it has got to be one of the most poory assembled books on Java I have seen. There are a few glimmers of intelligence in there, but as a whole the book collapses under its own poor organization. It's also for an older version of Java...

Hopefully the API listing is the only thing JDA has in common with Java Complete.

Book

[jbmoll]

How come people can keep creating new books on languages even though there are 10,000 books about it allready out there. They all pretty much repeat each other over and over. Use the newsgroups or web for some real help!

Re:comprehensive but somewhat redundant

[stratjakt]

You do realize that not every workstation has access to the web, espescially when you consider that java is an EMBEDDED platform.

And even those that do, it gets knocked out from time to time.

Plus, many developers (myself included) like to do the bulk of our stuff in a 'sandbox', completely disconnected from the network at large.

And how many programmers have WWW access in the toilet, where most research is done.

useful but a lot of redundancies

[hashmap]

I found the Almanach to be extremely useful in displaying the intended usage for many of the classes. Java builds on numerous desing patterns that can be overwhelming for a novice.

For example just browsing the API I had a hard time figuring out how to use the crypto package to encrypt data. The almanac shows that in ten lines.

In many respects the Almanach is superior to the "Java Cookbook" by O'Reilly because this latter spends way to much time on trivial implementations.

The aspect that I don't like is the huge index(or listing at the end whatever that is). I found that to be totally useless. There are dozens of methods with identical names anyway so finding the one you need is easier to do on the package level in table of contents. This index makes the book unnecessarily bulky.

i.

Why?

[naoursla]

Why would I ever need to buy a book with the Java api? They aren't updated, don't have hyperlinks, don't support copy/paste, don't open to the correct page when I press help, and aren't free.

very helpful book

[nuffle]

I have a copy of one of the earlier editions, and it quickly became one of the most ragged and tattered computer books i owned. Although there is more detailed info available in javadocs, having all the classes, methods, and members available in a print is very helpful. I found it much easier to quickly thumb to a certain class when I couldn't remember the order of some arguments or the name of an attribute.

Just note that no method or attribute descriptions are included in the book, just the method signatures or the attribute types. You have to already know basically what everything does (or be able to deduce it from names), and just use this to jog your memory. So despite what some other posters say, this isn't a beginner's book.

Don't waste the money

[Capt_Troy]

Save it for LOTR TTT...

I'm been tasked with Java development lately (and unfortunatly). In my experience, you buy a book detailing the Java API, then in half a year, it changes and your book is out of date and you can't use it for fear that you might end up using a depricated method. Just buy a java programming concepts book (but even these fade quickly) and use the Javadoc to get your API info. Spend the rest on movie tickets to support the MPAA (oops, did I say that?)

Re:Don't waste the money

[hosebee]

In my experience, you buy a book detailing the Java API, then in half a year, it changes and your book is out of date and you can't use it for fear that you might end up using a depricated method.

In my experience, you might want to get more experience.

• All the major java compilers have a flag to alert the user when he/she is using deprecated methods.
• The fact that deprecation is part of the language should tell you that Sun realizes forcing abrupt API changes is counterproductive.
• If you start/started with 1.2 or later, the number of deprecated methods you are likely to see or have to migrate is in reality very small.

Having said that, I do agree with you that you shouldn't waste the money; only because the full APIs are free (and usable via HTML) from Sun. Only someone with a paper fetish may want a hardcopy of the API. You should buy a book that deals in depth on a topic concerning you (JDBC, threads, beginning, etc.)

I carry knowledge of Java in my head for the same reason I carry a Leatherman: it's no good approaching every problem with only a hammer.

Remember, paper is just a tree recycled.

Re:Don't waste the money

[Capt_Troy]

Good points... My comments below:

All the major java compilers have a flag to alert the user when he/she is using deprecated methods.

This is true, however, better to use the non-depricated methods instead and if your reference is old, you won't be able to tell.

If you start/started with 1.2 or later, the number of deprecated methods you are likely to see or have to migrate is in reality very small.


I actually started with 1.1.6 and purchased an API book (stupid). Well, when 1.2 came out there was something like 2000 new classes and my books were totally useless. Since then, you are correct, very few depricated methods. But the book experience made me bitter :)

Re:Don't waste the money

[Capt_Troy]

It's quite embarassing when the only argument you can make against my comment is that I spelled a word wrong...

Why would I buy the javadoc?

[peterpi]

"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."

No! If the book was just what's here, it would be just a copy of information of information that is freely available on the internet!

So many books on Java seem to include a copy of the Javadoc documentation. It's just a con to make the book look bigger.

Well done Bruce Eckel for resisting this cheap tactic in the brilliant Thinking in Java.

Re:Why would I buy the javadoc?

[Felipe Hoffa]

Before writing that, did you consider that Thinking in Java is freely available on the internet?

Fh

Ps: Just to make it clearer, there might be reasons for buying a book composed of material that you may also get free on the Internet. According to Eckel's words, leaving the book online hasn't affected its sales.

Better than a copy of the API

[wormbin]

I see lot's of post saying things like why would I want to read this when I have the free 1.4 API javadocs online?

I agree. The best books aren't copies of the API that tell you all the good things about the language. The best books show you the warts and gotchas of the language. For C++ this book was Scott Meyer's Effective C++. Java has a similarly named and equally useful book Effective Java which I have found invaluable. Not as good but still worth the purchase price is Java Pitfalls

I haven't read More Java Pitfalls Has anyone read this? Is it any good?

Let me save you $24.99...

[dconder]

Section 1, 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.

All the examples.

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.

Java 1.4 spec.

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.

I guess you would have to figure this part out yourself, but what real value is it anyway?

I know, I know, it's nice to have this in book form, but the sooner you learn how to parse through what javadoc provides, the better. Especially if you are serious about learning/using java, you need to become familar with javadoc. Plus the APIs are still changing, and the Sun website will always have the most up-to-date information. It takes a while to get used to looking at documentation online, but once you are familar with it, you will be proficent in finding what you want in no time.

The real value of the books seems to be the examples, but they are all on-line too.

Seriously, don't buy this book. If you want something that will truely make you a better Java programmer, get Effective Java. That book is worth its weight in gold.

Re:Java in 6 easy steps

[photon317]

Oh fuck off loser. It was funny. And no, it's not from experience, I just made that up because I hate Java, in case you couldn't get that.

Re:Java in 6 easy steps

[photon317]

Still waiting for somewhere to send it, you dumb shit AC.

Re:Java in 6 easy steps

[photon317]

And I'd like to add that this last comment you made is getting a bit offensive now. In your world you're making a stupid comment about something fake. Over here in reality-land, you're talking about my future wife. Tone it down.