Rating: 
Summary: Seminal J2EE Patterns Work
Review: Seminal defined as...Highly influential in an original way; constituting or providing a basis for further development: a seminal idea in the creation of a new theory. For C, its K&N.
For C++, it's Stroustroup.
For SQL, it's Date.
For RUP, it's the 3 Amigos.
For patterns, it's the GoF.
For Java pattner, it's Grand. For J2EE, this is it.
Rating: 
Summary: What's the difference ?
Review: So ... what' the difference with the patterns in the java.sun.com site ?
Rating:
Summary: Great book about J2EE design!
Review: The beta version of the J2EE Pattern Catalog found on the Web, has evolved into this great book. The authors have made a nice job in categorizing and illustrating useful patterns for the J2EE platform. I recommend everyone that is involved with J2EE design to have a copy on the bookshelf. A pattern is a reuse mechanism and a way to facilitate communication between developers, designers, and architects. I believe almost every pattern presented in this book fulfil those requirements. The exceptions are Service to Worker pattern and the Dispatcher View patterns that are trying to resolve too much at one time. Dispatcher View, though, is a good name, but Service to Worker does not feel like a great pattern name. This book also contains a chapter about bad practice, which is as important as good practice. The authors are inspired by Martin Fowler's book about refactoring and have provided a chapter about how to refactor bad J2EE design into good J2EE patterns. Patterns are one of the best reuse mechanisms we have in the software community and I find this catalog of good, documented patterns very useful. I hope we will se more books of this kind in the future.
Rating:
Summary: A Must Have Book for J2EE Design and Development
Review: The design considerations, bad practices and solutions to common problems have proven to be priceless. These guys have obviously been in the real world, experienced real world problems and formulated real world solutions. This book is a "Must Read" for any group venturing into J2EE design and development. The ideas for this book began over 2 years ago. We hired the authors to assist our group in making some serious design considerations. While they were writing this book , they were working with us to help us implement our application using these patterns. We coded the application based on what we learned from the authors of this book. The result was a very successful J2EE web based application. We had 3 major functional releases of that system in a 6 month period utilizing the patterns discussed in this book. At the same time our group of 6 developers also cranked out 2 other support applications based on J2EE patterns. All of this in that 6 month window.
Using these patterns will do several things:
1. Provide a standard framework for application development
2. Help to decrease development time
3. Encourage tiny looseley coupled components
4. Simplify maintenance
5. Allow developers to more easily add new functionality to existing applications
If you are going to write J2EE applications... Get this book. Read it. Live by it.
Rating:
Summary: Excellent for architects and developers alike
Review: This book is a must if your are in the J2EE industry and unless you are content to being a head-down coder! All the architects and serious developers, who not only wants to make the sw work but wants to make it efficient and well-structured too, should go thru it, the examples are very helpful and categorizing the patterns in three different tiers provide a intuitive way to look at those. Without making this review any longer, what I'll suggest, NOT as a prerequisite, but as a supplement, is the Gang of Four's (Eric gamma et. al.) 'Design Patterns' book...
Rating:
Summary: A *Great* Collection!
Review: This book is a real all-star! It was an easy and enlightening read. I came across some very strategic patterns and implementation strategies. It expands on your patterns vocabulary and would be a great help to J2EE architects, designers & developers in enhancing their design skill-set. I was mightily influenced by this book and trust me, you will be too!
Rating:
Summary: Essential reading for J2EE developers
Review: This book is about server-side Java development under J2EE. It presents a collection of design patterns, the names of which are well known in the Java development community and referenced in other J2EE texts. If you plan to do J2EE development, this book serves as an excellent introduction and catalog of these "best practices" design patterns. Also interesting about this book, is its presentation of the J2EE architectural model as having three logical tiers: the presentation tier, the business tier, and the integration tier. Design patterns are presented in terms of these tiers. Preceding the pattern catalog, the authors present a section on bad practices (also arranged by tiers) and a set of refactorings to remedy those bad practices. This is a good section to help you recognize where your current design is weak and what exactly makes it weak. Mixed in throughout the text are recommendations on the proper use of EJB's, and this is the only caution I have about this book. It was written around the time of J2EE 1.2, prior to Message Beans and the improvements in Container Managed Persistence (CMP 2.0) that appeared in J2EE 1.3. Some design recommendations may be out-dated, but the patterns still hold true.
Rating:
Summary: Excellent how to design book
Review: This book is an excellent guide for how to design J2EE applications. It is well organized and extremely practical. If you are fortunate enough to be starting from scratch, it will give you a clear roadmap for how to build your app right the first time. If you're not so lucky and have to pick up the pieces of an existing app, the refactoring suggestions give excellent direction on how to get your app from where it is to where it should be. So, whatever your situation, this book will help!
Rating:
Summary: Great book for designing enterprise level applications
Review: This book is great for making decision regarding enterprise level scalable distributed applications. It provides answers to the designers for what they need while making design decisions regarding scalability, coupling, reusability, maintainability and much more. It also discusses common mistakes a software designer can do. I highly recommend this book for every J2EE application architect & developer.
Rating:
Summary: Must Have J2EE Book
Review: This book is the best J2EE book I have come across since started working with J2EE a few years ago. There are may other books that talk about technology and API and stuff. But, what this book does is go beyond that and talk about the best practices and patterns that aid you in using the technology. I particularly liked the refactorings, though after being involved with many J2EE application architecture/design, some of this was a validation of how I had done my own design and improvements. These J2EE patterns are also something I have used in the past, but naming and the way the authors have catalogued it makes it very useful for me to document and describe the design. It also streamlines the way my team works since a lot of fluff is eliminated in the design document and communication by using the patterns which encapsulate the details! On the minus side, the last chapter could be a little more detailed and the pictures in that chapter could be more clearer. I think the last chapter only brushes the tip of the iceberg. It should have elaborated a more complete application. But then, it does give you some direction. Overall, I rate this book as 5 Star/Excellent. I only wish I had this book when I started to do J2EE programming/development years ago. So if you are getting into J2EE or have been doing J2EE for a while, go get this book. It saves a lot of time and trouble!
| 
