登録情報
|
プレゼンテーション層で利用されるデザインパターン、ビジネス層のパターン、データベースアクセス、O/Rマッピングのテクニック、メッセージングに関するパターン等です。文章、ソースコード、クラス図、シーケンス図が使って説明されています。なぜ、このようなパターンを使うのか、その効果等が丁寧に説明されています。文章の量が、ソース等に比べて多く、しっかり説明してある印象でした。
最後に、アンチパターン~よくやる失敗例~の説明もあります。
EJB等J2EEの仕組み等の説明は、ほんの軽くしかのってないので、ある程度J2EEの知識があって読む本でしょうか。
個人的には、オライリーの本は、ちょっと苦手なんですが、この本は、比較的読みやすかった印象です。
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
My criticisms are minor. The first chapter which covers J2EE basics (probably unnecessarily) could have spent a little longer on it's description of UML. The technical points on CGI are in error, and the traffic estimates are inflated well beyond where people will see scalability issues in production, especially with resource intensive application servers.
There are several critical Java design works, including Bitter Java and Bitter EJB. This book is at the level of those works. It even references Bitter Java in a later chapter on Anti-patterns.
|