Rating: 
Summary: Good book for J2EE Design
Review: This book is the GoF book for J2EE. Its part 2, Design Considerations, Bad Practices and Refactorings, is especially interesting. As we know, good design often does not come at first, it comes after several refactorying, this part explains
how to apply J2EE Patterns by refactorying. Its Part 3, Chapter 6, Patterns Overview, is a very good summary as well. You can find A J2EE Pattern Relationship in Figure 6.2, which is worth reading again and again. Table 6-6, 6-7, 6-8 tell you which pattern, on which page you can use for a special problem you face. There is a case study in Epilogue, it's good but a little light, hope more cases studies can be added in the next edition. Some patterns changed a little for EJB2.0, for example, Composite Entity uses dependent object in EJB1.x, and it uses local interface in EJB2.0; Service locator is used in Message Driven Bean in EJB2.0 now. Since this book was based on EJB1.1, EJB2.0 related features are not included. This book can discover more relationships between different tiers, for example, View Helper pattern can use
Value Object, the idea of Business Delegate can be used in other tiers as well, etc. In a whole, it's a book worth studying carefully.
Rating:
Summary: *THE* guide to applying patterns in J2EE projects
Review: this book is very well-written and loaded with practical advice. excellent design patterns are illustrated thru concise and relevant examples. one of the virtues of programmers is laziness. reading this book and applying the design pattern solutions can save us a lot of work in head-starting an architecture for a project. think in high-level design patterns instead of low-level details of finding the right data and methods, your life will be better off!
Rating:
Summary: A great achievement
Review: This book provides two important services: 1) it catalogues the important patterns for modern object-oriented server development 2) it concretely describes these patterns in the context of J2EE technologies. As a bonus, it clearly describes the motivations and reasons for refactoring existing services - something difficult to explain to management. There is a wealth of practical experience expressed in these pages. It does not focus on code examples, but there is easily enough code provided to "get the idea". I, for one, find tedious those books that emphasize page after page of code instead of the concepts and design principles illustrated by the code. This book emphasizes design rather than coding, and provides clear explanations of the reasons for and advantages of certain design decisions. I consider this book one of the most important computer books I have bought in recent years. It will have a long shelf life - unlike most books I buy these days.
Rating:
Summary: Great J2EE Design Book
Review: This is a great book. I really liked the title, but was afraid I would be let down - luckily I was not. This is not a "learn J2EE book", but rather a book on how to design J2EE applications. Something the J2EE community has been waiting for, for some time. I am glad Sun finally released it. My team has used many of these patterns, but never actually had a name for them. What I like most about the book is now I can talk about designs in the form of these patterns and not have to convince my team each time. These patterns are highly credible, useful and have never been challenged by my team - which save me a great amount of time. Ever J2EE designer/architect should get this book.
Rating:
Summary: Sure to become a seminal J2EE reference title.
Review: This work provides key design idioms for the J2EE platform, and therefore promotes the maturity of the platform for serious architects and designers. The 15 patterns are presented clearly, delineated into logical tiers (6 presentation, 7 business and 2 "integration" tier) together with well-reasoned rationale. There is also a refactoring session which, although not comprehensive, provides a road-map for moving existing implementations to this pattern-oriented new world. I would expect this work to become synonymous with well-architected J2EE systems, and perhaps to provide the motivation for architectural review of existing systems. In particular these patterns provide obvious advantages for reuse and maintainability. At the very least they provide a common grammar for communicating design concepts. The sample source code is useful as a starting point on its own.
| 
