Rating:  - Provides solid foundation for layering and interfaces
This is a great book for providing the foundations and beginnings for which you should approach projects. The book's main purpose is to re-inforce rules/guidelines for encapsulating the tiers of an application. The most important concept to take away from this book is: encapsulate complex api's and container dependant code in their specific tier and expose input/output from these tiers using basic api's. This allows you to loosely couple the tiers (good for maintenance) and at the same time reduce security risks by not exposing business logic where you don't need to.
Now for some critiques...A lot of the pattern examples are not fleshed out. In some cases even the code that is provided has mistakes in it; however, the patterns are right-on and that is what this book is all about. So, don't take the syntax of the example-code provided too literally. Some of the Presentation Tier content is obsolete given advances in IDEs which generate a good deal of the patterns described for you (but still good to know why/how things are done even if they're automated). I found the chapters covering the Business Tier and Integration Tiers to be most valuable.
All-in-all this is a valuable read and reference for app. developers.
Rating:  - must have j2ee book
I have been involved in a java application architect role for many years now and my app development has been successful and the reason is I always choose and follow pattern-oriented application development for building all crucial aspects of application. This patterns book is another gem in my collection. In this book, the authors cover extremely well on numerous design issues with j2ee application that developers face every day. With this book in hand, a java architect would able to build j2ee applications pretty quick by using appropriate patterns. this is one of most recommended book for all our guys invoved with j2ee development project. In all, this book is must-have to become a expert on J2EE.
Rating: - Excellent J2EE book
I usually don't buy technology books as they are very short-lived and gets obsolete. This is the first J2EE book I bought this year and I am very impressed. There are a large number of Design Patterns books available in the industry over the last decade. Core J2EE Design Patterns offers the best solution catalog for building J2Ee applications in both a practical and readable manner. Instead of just another high-level catalog of design patterns, it provides insight into the real world scenarios of where these patterns can be employed. From a J2EE designer perspective, this book is a great addition to your portfolio.
Rating: - My favorite J2EE book
THE book to understand and use J2EE patterns effectively! Excellent concept introduction to begin with, to tide over the pattern non-gurus, comparison with established OO design patterns to ones mostly used in the J2EE community including ones on theserverside.com, plenty of demonstrable code some of which found their way into our deployed apps, great emphasis on patterns applied to specific layers of an application like ejb persistence, web etc. Great insight into usually tricky topics.
An excellent addition to anyone's J2EE repertoire. Truly worth the money.
Rating: - A must but not very well written
If you are a J2EE architect/developer, then you must read this book. It provides the most important and relevant patterns in J2EE design and development. I would say this book is as important as the "Design Pattern" book from the Gang of Four.
However, I'll recommend this book with reservations. It was not very well written and I had to read several times before I could understand each of the patterns, understanding that the authors were Sun employees who were more used to coding than writing a book.
Another week point is this book recommends the full use of EJB, even though if you've programmed with EJBs before, you'll know how hard it is to write EJB beans. In fact, many people consider EJB the greates failure of all J2EE components (that's also why they are ditching remote and home interfaces in EJB 3 and make entity beans POJOs).
Having said that, you still can learn a lot of things from this book.
|
