| FlazX | Browse Computer Book | Community Board | Links | Blog | Login |
|
J2EE Design Patterns Applied Google Search |
The tendency for any book on software patterns is to dissolve into software engineering jargon, and you'd expect this title to do the same given the abstract names for many patterns listed in its early sections (for example, `Intercepting Filter,` `View Helper,` and `Service-to-Worker` are hardly catchy names). While the authors do provide the `official` UML and pattern descriptions for these J2EE patterns, the real surprise is that they use a handful of longer case studies to show off each pattern in action. First there is a hotel booking application to show off Web tier patterns. Next comes an excellent case study on persistence patterns used to simplify working with EJBs and databases. Patterns for improving performance and scalability are illustrated with a travel booking application. In each case, the authors manage to introduce a number of important patterns while anchoring their presentation with a practical and interesting discussion of real applications. This approach makes this title succeed on several levels, both in presenting essential patterns and demonstrating how these designs often work together in real Web solutions. The end result is a text on software patterns that provides some of the best thinking on J2EE design today in a remarkably readable and engaging format. In all, this title will be absolutely required reading for anyone who lays claim to be an expert on today's J2EE platform. --Richard Dragan This book is about code - about %90 of the pages have source. Perhaps the first book I ever seen that has compilable, working code. Also, I think the examples and interfaces in this book are much better than the Core book. In short, if you have the core patterns book and are stuck, this indeed could be exactly what you need. I would say you could skip that book and start with this one. I've read a lot of patterns books. Most didn't really help. Some got me to the point of asking new questions. This book, and `design patterns explained`, are in my view indispensable classics. They left me with a clear understanding of what I was trying to learn. One negative point: I read the comparison between `service to worker` and `dispatcher view` several times and I still don't get what they are trying to say. This is one of the few places in the book where there is no code, and it probably could have helped me here. To be fair, it does have some nice sequence diagrams but its seems lacking compared to the rest of the book. This book starts where `Core J2EE Patterns` ends. Instead of being one more book on patterns catalog and snippet code, it plucks related patterns and weaves them into a framework. This framework-oriented approach starts with the simple but pertinent observation that standard J2EE patterns like Service-to-Worker and Dispatcher View can be reinterpreted as micro-frameworks and continues throughout the rest of the book. For example, chapter 3 combines 3 patterns( DAO, VO, Service Locater)together to lay the foundation of a persistence framework. Another positive aspect of this book is that it devotes complete chapters to security and integration patterns.Of late, integration patterns have become important enough to merit a web site of their own ( integrationpatterns.com ) and it is quite hard to find other good references on security patterns. Thus this book has a lot of new things and perspectives to offer and deserves more attention than it seems to be getting. Finally a criticism : This book mentions other books by name and ISBN numbers without mentioning the author(s) of the books. This is the first time in my life I have seen such a practice. This is definitely a bad practice and an antipattern and a cruelty to poor authors who deserve to be mentioned by name. This book presents patterns inside frameworks, so you can The web tier chapter details patterns that could be used for request processing with session management, view manipulation, validation and security. The persistence framework chapter was perfect for our implementation with its data access layer strategy based on DAOs and value objects, though we would have liked to see some transaction management patterns. The scalability and performance concerns have been closely investigated, as have all security designs like single-access, check-point and role patterns. A working example targeted for a leading app server could have proved useful here, though there is plenty of code available for download. After all is said and done, the chapter on integration where everything comes together nicely, scores top marks for topics not usually found in other books. Other books on J2EE |
Google Talk : admin-at-flazx-dot-us