J2EE Design Patterns

J2EE Design Patterns
William Crawford, Jonathan Kaplan
24 Sep 2003
Purchase online

Architects of buildings and architects of software have more in common than most people think. Both professions require attention to detail, and both practitioners will see their work collapse around them if they make too many mistakes. It's impossible to imagine a world in which buildings get built without blueprints, but it's still common for software applications to be designed and built without blueprints, or in this case, design patterns.

Page 2 of 2
  1. Editorial Reviews
  2. Customer Reviews

Customer Reviews

Prasad Reddy said
This book could be an introductory book on understanding J2EE design and guiding principles but beyond that you don't find much help. The book has poor editing and repetitive style of explaining concepts which annoys experienced J2EE developers. If you are looking for J2EE patterns to support real-world implementation with exhaustive details then you must consider reading Core J2EE Patterns (Alur), Core Security Patterns (Steel) and Enterprise Integration Patterns (Houpe).

calendarw said
It's good for me because I'm still a beginner of J2EE, its focus on using servlet, jsp and JavaBeanIt's good for me because I'm still a beginner of J2EE, it focuses the patterns on using Servlet, JSP and EJB, it told that how to determine and improve scalability and extensibility, and how to model and implement the system. It is used UML diagram for represent the pattern; some of example covers few chapters to let the content easy to study, some of code is very common for let reader reuse in different application.


francis said
There are a large number of Design Patterns books available in the industry over the last decade. Crawford and Kaplan's J2EE Design Patterns offers a fresh look at the subject in both a practical and readable manner. Instead of just another 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 the study desk.

There is nothing remarkable about this book. It loses momentum about halfway through. It isn't a big book and there doesn't seem to be much depth in the coverage. Look else where.

Ajith Kallambella said
Old wine in a new bottle. Put simply there's nothing new in this book.

If you are just beginning to wade through the vast land of J2EE, you will find lots of introductory material to help you get started. The preface pronounces the audience as Java-aware readers who may not be fluent with J2EE technology stack. Beginners will appreciate the slow pace, logically ordered chapters, thoroughly descriptive background information on every pattern presented and an entire chapter dedicated to UML. However, if you are familiar with the core J2EE patterns published by Sun, there aren't a lot of things in this book that will interest you. Some things worth mentioning are - strategies for content caching, Serizized entity strategy for rapid development, and use of soft references for being thrifty on memory usage. The chapter on Enterprise Messaging Patterns is particularly interesting since it is an area that has attracted some interest lately.

Why another book on patterns? The bookshelves are already packed with several noteworthy titles on this subject and it is only natural to expect to see something new in new titles. This book is a far cry from "CoreJ2EE Patterns" or even the "Java Enterprise Best Practices" from the same publisher.

They could have done a better job by cutting down on teaching the basics and including all of Core J2ee patterns. ACID transaction pattern isn't a pattern at all, but just a fundamental concept. The selection of best practices covered seems arbitrary at best.

- Ajith Kallambella

You might also like...



Why not write for us? Or you could submit an event or a user group in your area. Alternatively just tell us what you think!

Our tools

We've got automatic conversion tools to convert C# to VB.NET, VB.NET to C#. Also you can compress javascript and compress css and generate sql connection strings.

“Better train people and risk they leave – than do nothing and risk they stay.” - Anonymous