|Amazon Price||New from||Used from|
It does not just discuss technology, but stress its practical application. The book is driven from the need to solve common tasks, rather than by the elements of J2EE.
It discuss risks in J2EE development
It takes the reader through the entire design, development and build process of a non-trivial application. This wouldn't be compressed into one or two chapters, like the Java Pet Store, but would be a realistic example comparable to the complexity of applications readers would need to build
At each point in the design, alternative choices would be discussed. This would be important both where there's a real problem with the obvious alternative, and where the obvious alternatives are perhaps equally valid
It emphasizes the use of OO design and design patterns in J2EE, without becoming a theoretical book --This text refers to an alternate Paperback edition.
The results of using J2EE in practice are often disappointing applications are often slow, unduly complex, and take too long to develop. I believe 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.
In this book I offer a real-world, how-to guide so that you can make J2EE work in practice. I draw on my experience of designing successful high-volume J2EE applications and salvaging failing projects, as well as intimate knowledge of the J2EE specifications.
Ill help you to solve common problems with J2EE and avoid the expensive mistakes often made in J2EE projects. I 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. I take a practical, pragmatic approach, questioning J2EE orthodoxy where it has failed to deliver results in practice and instead suggesting effective, proven approaches.
What you will learn from this book
"I just wish this book had been around earlier when I was starting enterprise Java development. This book shows the benefits and pitfalls of J2EE and how best to avoid them."
Andrew J. Smith, Java Architect
"Rods depth and breadth of experience is quite impressive! J2EE developers can avoid many of the hard lessons Rod learned by reading this book."
Todd Lauinger, Software Construction Fellow, Best Buy, Inc.
It does not matter you love or hate EJB; any serious enterprise java application developers/architects should have this book, reat it, put it on your desk.Published on April 12 2012 by BK
There's no doubt that Rod knows what he's talking about. Much of the book contained best practices that were incredibly valuable, and he seemed to have a focused direction that he... Read morePublished on May 27 2004 by Melvin
This is one of the best technical books I've ever read, regardless of topic. Johnson has an amazing technical mind and is a great writer, to boot. Read morePublished on May 15 2004 by Michael A. Thomas
Great discussion of J2EE design and development. This is not a beginners book. It has a lot of great material on the pitfalls of J2EE development and how to avoid the traps. Read morePublished on May 2 2004
When I first heard about my coworkers talking about this book, I thought "oh great, another J2EE book! Read morePublished on July 25 2003 by John D
I chose this book because it was the No.1 best-selling book at amazon and I was not disappointed. In fact, this is one of the best architecture cum programming books I've read. Read morePublished on July 10 2003 by David Wong
I have a lot of books, this is the best book I had never. This book is not a theorical book, no, it offers a lot of experience tips and definitions that can convert you to a true... Read morePublished on May 15 2003
I have a lot of books and it is the best book I had never. This book is not theorical, no, it offers lots of experience, tips and definitions that can convert you to a true j2EE... Read morePublished on May 15 2003 by LUIS LOPEZ PEIRO
It's not an average J2EE book . Rod discussed a lot of framework design issues. He also criticized some J2EE flaws and told us how to avoid them. Read morePublished on April 23 2003 by Huang Teng Shiu