What is this book about? The results of using J2EE in practice are often disappointing: applications are often slow, unduly complex, and take too long to develop. Rod Johnson believes that the problem lies not in J2EE itself, but in that it is often used badly. Many J2EE publications advocate approaches that, while fine in theory, often fail in reality, or deliver no real business value. Expert One-on-One: J2EE Design and Development aims to demystify J2EE development. Using a practical focus, it shows how to use J2EE technologies to reduce, rather than increase, complexity. Rod draws on his experience of designing successful high-volume J2EE applications and salvaging failing projects, as well as intimate knowledge of the J2EE specifications, to offer a real-world, how-to guide on how you too can make J2EE work in practice. It will help you to solve common problems with J2EE and avoid the expensive mistakes often made in J2EE projects. It will guide you through the complexity of the J2EE services and APIs to enable you to build the simplest possible solution, on time and on budget. Rod takes a practical, pragmatic approach, questioning J2EE orthodoxy where it has failed to deliver results in practice and instead suggesting effective, proven approaches. What does this book cover? In this book, you will learn Who is this book for? This book would be of value to most enterprise developers. Although some of the discussion (for example, on performance and scalability) would be most relevant to architects and lead developers, the practical focus would make it useful to anyone with some familiarity with J2EE. Because of the complete design-deployment coverage, a less advanced developer could work through the book along with a more introductory text, and successfully build and understand the sample application. This comprehensive coverage would also be useful to developers in smaller organisations, who might be called upon to fill several normally distinct roles. What is special about this book? Wondering what differentiates this book from others like it in the market? Take a look:
I had been using Spring Framework professionally for almost around two years and decided to read this book because I was having problems understanding Spring in the big picture the more I use it. This book explains many underlying designs and decisions made in the framework. It helped me understand deeper how Spring creates beans and application context, how Spring manages transactions, and how Spring integrates web frameworks. This book also gave me the feeling of how complicated EJB was even when I had never used it before.
The problem with reading this book at the time of this writing is this book is outdated since the Spring Framework has changed dramatically. One other issue I had was this book tries to justify Spring design decision by comparing it EJB thus devotes a large amount of text to EJB. As someone who never used EJB before and expecting the book about Spring Framework, it was not a pleasing experience.
Only read this book if you want to know the history of the Spring Framework.