J2EE Development without EJB Chinese Edition

Author: (USA) Jason Herrus
Publisher:
Publish Date: 2005-09-01
Features: At first glance, the title of this book, Expert One-on-One J2EE Development Without EJB, doesn’t seem too striking. After all, there are already too many books about J2EE, and without EJB seems a bit like deliberately provoking EJB. How could a J2EE book possibly bring about a shock to belief or thinking? But it did. It not only made itself an immortal classic but also made Rod Johnson my new idol for the past year. --xiecc
Is your J2EE project consuming too much of your time? Are they difficult to debug? Are they inefficient? Maybe you’re still using traditional J2EE solutions, but these are too complex and not truly object-oriented. Many of these problems are related to EJB: EJB is a complex technology, but it hasn’t fulfilled its promises. In this hands-on guide, you’ll see a completely different approach: creating higher-quality applications without EJB, with lower time and cost. You’ll learn how to make full use of various practical techniques and tools, including the popular Spring framework and the open-source tool Hibernate. You’ll see how to efficiently solve core enterprise-level application problems, such as transaction management, persistence, remote calls, and web design. You’ll understand how this new approach impacts testability, performance, and scalability, and experience firsthand how lightweight architectures can significantly reduce the time and effort required for project development.
Since the release of J2EE technologies like servlets, EJB, and JSP, the authors of this book, Rod Johnson, have been using these technologies. He knows the pros and cons of these technologies inside out. Now, through this book, you can share his expert experience face-to-face. You’ll learn how to find the simplest and most maintainable architecture for your applications; how to manage transactions effectively without EJB; how to use AOP and IoC to solve common problems in enterprise-level software development; web-layer design, including the role of the web layer in well-designed J2EE applications; effective data access techniques in J2EE applications, including JDBC, Hibernate, and JDO; how to use open-source products to boost productivity and reduce coding; and how to improve performance and scalability from a design perspective.
Traditional J2EE design approaches, especially EJB, are increasingly frustrating for architects and developers. This book is written for those people. It will tell readers how to replace EJB with clearer, more efficient solutions starting now and begin to move toward a new era of web applications.
This book has a lot of "selling points." For example, its author, Rod Johnson, has 10 years of experience writing Java programs and is currently a member of the JSR expert groups for servlets and JDO 2.0. Another selling point is that the book focuses on popular open-source frameworks like Spring, Hibernate, and WebWork, as well as trendy concepts like IoC and AOP. The biggest selling point, however, is boldly displayed on the cover of this book: without EJB. We’ve seen countless books and articles claiming that EJB is one of the core technologies of J2EE, but Rod Johnson’s book boldly claims that most J2EE applications don’t need EJB at all. This almost provocative stance makes any responsible J2EE architect unable to resist the urge to explore—whether they plan to agree with him or disagree. But none of this is the greatest value of the book.
What is the basis for choosing an architecture or technology? Rod Johnson believes it should be based on practical evidence, experience from historical projects, or personal experimentation, rather than any form of idol worship or factionalism. The book discusses problems and solutions in all aspects of enterprise applications, and all these solutions are products of this "evidence-based approach."
In addition to providing these solutions to readers, Rod Johnson hopes to convey a more important message through this book: the "evidence-based" way of working—that is the way programmers should work.