AnyBook4Less.com	Find the Best Price on the Web Order from a Major Online Bookstore
Home  |  Store List  |  FAQ  |  Contact Us  |
Ultimate Book Price Comparison Engine Save Your Time And Money Keyword AuthorISBN

Title: Java Application Frameworks by Darren Govoni ISBN: 0-471-32930-4 Publisher: John Wiley & Sons Pub. Date: 11 June, 1999 Format: Paperback Volumes: 1 List Price(USD): $44.99

Your Country USA Canada United Kingdom Australia Austria Belgium France Germany Italy Netherlands Switzerland Currency AutoUSD CAD GBP EUR AUD CHF Delivery Only cheapest delivery All delivery options Include Used Books Are you a club member of: Barnes and Noble Books A Million Chapters.Indigo.ca

Average Customer Rating: 3.17 (6 reviews)

Rating: 4
Summary: Nice introduction to frameworks
Comment: I guess framework is now a buzzword in the IT market. If you want to know more about it, read this book.

Java Application Frameworks is a necessity for managers as well as developers diving deep into the development of applications. It introduces to the reader basic application concepts as well as introduces some well known java frameworks like collection framework, infobus etc. For framework developers, it introduces them to the details of constructing and designing one. If you are diving into building a framework, read this book first.

This is definitely a book that is worth the money.

For readers who wants to know more about application framework, read the book "Building Application Frameworks" by Mohamed E Fayad, Douglas C. Schmidt, Ralph E. Johnson.

Rating: 1
Summary: Utter waste
Comment: Basically, what this book does is repeat a message any decent Java programmer already knows: use interfaces instead of implementations. It wraps this message in a variety of incomprehensible disguises. But Govoni doesn't even follow his own advice: in his thoroughly botched description of the Java Collections API, he repeatedly uses concrete implementations (ArrayList, HashMap, etc.) to declare collections. You are supposed to use the interfaces (List, Map, etc.) to declare, mentioning the concrete implementation only when the object is constructed, so that your whole program doesn't become dependent on which implementation of a collection you are using. In other words, say:

(1) List l = new ArrayList();

Not:

(2) ArrayList l = new ArrayList();

It is extremely appalling that Govoni writes every single Collections example using the approach of (2), not one. He can't even follow his own, repeated-to-the-point-of-idiocy advice. This is what happens when publisher greed, Java hype, Design Patterns hype, and a bad author all get together.

Rating: 5
Summary: Not for those needing hand holding
Comment: If you want a book that gives you all the source code you need to reuse its concepts without understanding them, this book is not for you.

However, if you know what is going on and understand the big picture, this book is a keeper.

This book introduces a line of thinking that enables you to be a "next level" developer.

If you are a guy that is simply an implementer and want juicy examples to steal, then this book isn't for you.

By the way, the impact of Kevin Trent Smith on this book cannot be missed or ignored!