Slashdot Mirror
Apache Jakarta Commons
What's To Like
The book takes the reader on a journey through the Jakarta Commons. The Commons is like a massive utility library of Java code. Much of the code has been promoted out of the other Jakarta projects as it became more useful. One of the first such components was the Digester, which is a component to initialise a Java object from the contents of an XML configuration file. Very useful, originally from Struts and now used extensively by other Jakarta projects.
As the subject matter for a book, the Commons seems like a natural winner (I guess I have to say that!). There are so many components in the Commons that a guide to their types and usage does need to be available for developers.
Naturally, the book has a website to accompany it.
What's To ConsiderWhere to begin? I was actually surprised to find that I did not care for this book. The last review I wrote was for Mr. Iverson's very good Hibernate book. That was well written and structured. Unfortunately, this book feels kind of thrown together. The lack of care shows in the cramped layout and typesetting, the over-abundance of UML diagrams (a few here and there are great, but this felt like padding), code examples that can only be described as under-whelming and an approach that feels like an annotated telephone directory.
Despite the lack of quality of the primary chapters, they only actually account for the first 199 pages of the book. This is actually a very reasonable number of pages for a book, especially when you consider that classics like the first edition of Kernighan and Ritchie's "The C Programming Language" weighed in at about 220 pages. Sadly, the book then goes on for another 125 pages churning out what looks like repackaged JavaDoc for each of the major classes in the commons. You may like this, but it annoys the beans out of me and it'll reduce the score on one of my reviews faster than the Linux community can debunk a SCO IP infringement claim.
SummaryI really wanted to like this book. But it feels like someone was cranking the handle on a cash machine and thought that if they printed stuff about Jakarta, that the geeks would obediently buy it. Not this time. There are other books about the Jakarta Commons; buy one of those."
You could purchase Apache Jakarta Commons - Reusable Java Components from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
If you go through the Barnes & Noble link for the book, you'll find that the book costs $31.99 for the unwashed masses, and $28.79 for the "B&N members". What Barnes and Noble isn't telling their members is that they are still paying more than if they went to Amazon! Even with an associate laden link, you can still get the book off of Amazon for a mere $26.39! And no membership hassles to mess with!
From an Amazon review:
Note that this 325-page book is really a 201-page book. Appendix A is the entire API of the Commons lang project - word for word.
Am I the only one who gets annoyed at how computer books have devolved into hardcopies of auto-generated online documentation? Am I the only one who remembers books that cover the intangables of coding (e.g. theory of operation, correct methodology for usage, cool coding and hardware tricks, etc.) rather than the "instruction manual for dummies" books? Bah, I say! I don't know which is scarier: the current trend in books, or the fact that the review I'm citing gave the book 4 out of 5 stars.
Of course, I'll probably get in trouble with my fellow authors for saying this. (Sorry guys, but I just don't like 90% of the books being printed.)
Javascript + Nintendo DSi = DSiCade
This has to be among the worst booke reviews I have ever seen on Slashdot. And that's saying something. Most reviewers take the time to give you some detail. An indication of whether or not this book is for you. This just seems like a shameless whoring to get affiliate credit with B&N under the guise of a book review.
"I'd rather be a lightning rod than a seismometer." -Ken Kesey
Stop reading it the minute you realize it's shit.
Next time, spend less effort writing about your own involvement and more time on that of the authors of the book.
Raise your children as if you were teaching them to raise your grandchildren, because you are.
:-)
I wrote a book on the Jakarta Commons - The Jakarta Commons Cookbook, and, from what I hear people like it. Really, you should read it, I tried to stay as far away from reference as possible and pack it full of useful recipes.
------ Tim O'Brien
I think that's the first question any book like this would have to answer. Free and reasonably comprehensive documentation is included right along with all of these libraries. Why pay for anything more?
The answer is likely to be in tutorials or teaching narrative. I bought the OpenGL Guide for that to learn OpenGL because the API was a nasty maze to navigate otherwise. I don't think Jakarta Commons have that problem and I don't expect I'll be buying a book about them.
Start Running Better Polls
I would just like to respond to the bit about "cash cow":
;)
1. The book itself is published under an open license - the material in the book will be available as a free electronic download in a few months.
2. Yes, the last 125 pages *is* (for all intents and purposes) the printed javadoc. This was included at the request of the publisher, and it is valuable for some people.
So... I don't know how negatively the review was influenced by the inclusion of the Apache material, but it is entirely above-board per the Apache license and essentially reciprocal - I'm giving the material in the book back to the community via a free license to download the material.
Oh, and as an FYI, book writing is hardly a cash cow - I only wish.
If folks have any questions (e.g. why the delay in making the electronic version available? What is the state of affairs for tech book publishing? Why aren't you rich writing books yet?) let me know...
Cheers & best wishes,
-Will Iverson