DescriptionWhat is this book about?
Expert One-on-One J2EE Development without EJB shows Java developers and architects how to build robust J2EE applications without having to use Enterprise JavaBeans (EJB). This practical, code-intensive guide provides best practices for using simpler and more effective methods and tools, including JavaServer pages, servlets, and lightweight frameworks.
What does this book cover?
The book begins by examining the limits of EJB technology — what it does well and not so well. Then the authors guide you through alternatives to EJB that you can use to create higher quality applications faster and at lower cost — both agile methods as well as new classes of tools that have evolved over the past few years.
They then dive into the details, showing solutions based on the lightweight framework they pioneered on SourceForge — one of the most innovative open source communities. They demonstrate how to leverage practical techniques and tools, including the popular open source Spring Framework and Hibernate. This book also guides you through productive solutions to core problems, such as transaction management, persistence, remoting, and Web tier design. You will examine how these alternatives affect testing, performance, and scalability, and discover how lightweight architectures can slash time and effort on many projects.
What will you learn from this book?
Here are some details on what you'll find in this book:
- How to find the simplest and most maintainable architecture for your application
- Effective transaction management without EJB
- How to solve common problems in enterprise software development using AOP and Inversion of Control
- Web tier design and the place of the Web tier in a well-designed J2EE application
- Effective data access techniques for J2EE applications with JDBC, Hibernate, and JDO
- How to leverage open source products to improve productivity and reduce custom coding
- How to design for optimal performance and scalability
Chapter 1: Why “J2EE without EJB”?
Chapter 2: Goals.
Chapter 3: Architectures.
Chapter 4: The Simplicity Dividend.
Chapter 5: EJB, Five Years On.
Chapter 6: Lightweight Containers and Inversion of Control.
Chapter 7: Introducing the Spring Framework.
Chapter 8: Declarative Middleware Using AOP Concepts.
Chapter 9: Transaction Management.
Chapter 10: Persistence.
Chapter 11: Remoting.
Chapter 12: Replacing Other EJB Services.
Chapter 13: Web Tier Design.
Chapter 14: Unit Testing and Testability.
Chapter 15: Performance and Scalability.
Chapter 16: The Sample Application.
Chapter 17: Conclusion.
“…a valuable learning experience all round” (Application Development Advisor, 1st September, 2004)
|108||Change in Wording,2nd paragraph (1st bullet), 2nd-to-last sentence: ... Spring Framework can deliver declarative transaction management without AOP. |
without should be using
|262||Second paragraph,Was transaction tcript . It should read transaction script (i.e. script NOT tcript).||10/15/04|
|353||Last paragraph,Change this: Spring offers more options for managing the lifecycles of managed OPTIONS to this: Spring offers more options for managing the lifecycles of managed OBJECTS||10/15/04|
|531||Misspelled Name,Martin Fowler's name is misspelled as Martin Fower .||9/1/05|