Enterprise JavaBeans™ Component Architecture: Designing and Coding Enterprise Applications
✍ Scribed by Gail Anderson, Paul Anderson
- Book ID
- 127444184
- Publisher
- Prentice Hall PTR
- Year
- 2002
- Tongue
- English
- Weight
- 2 MB
- Category
- Library
- ISBN
- 0130355712
No coin nor oath required. For personal study only.
✦ Synopsis
This book simplifies the creation of well-designed enterprise applications using the upgraded Enterprise JavaBeans 2.0 specification. Experienced Java platform mentors Gail Anderson and Paul Anderson use detailed code examples to introduce every key skill involved in creating components, stand-alone Java platform clients, and JavaServer Pages API clients. They introduce powerful EJB platform design patterns, and show how to apply them in real-world projects while avoiding critical errors in application design. Using actual business components, the authors show how to make the most of these key EJB component architecture features: Stateless and stateful session beans Entity beans with bean-managed persistence Entity beans with container-managed persistence Container-managed relationships Local and remote interfaces The Enterprise JavaBeans Query Language EJB 2.0 specification message driven beansEach chapter includes a "Design Guidelines and Patterns" section designed to help you assess tradeoffs associated with your design decisions, and key point summaries that tie together important concepts. In short, Anderson and Anderson give you everything you need to build EJB 2.0 platform applications with maximum robustness, scalability, and performance.
📜 SIMILAR VOLUMES
The Java(TM) 2 Enterprise Edition (J2EE) platform connector architecture is the key component in Java's support for enterprise application integration (EAI) and for linking enterprise information systems (EISs) with Web services. Because many services are now provided through the Web, it is essentia
Many enterprises unfortunately depend on software that is insecure, unreliable, and fragile. They compensate by investing heavily in workarounds and maintenance, and by employing hordes of "gurus" to manage their systems' flaws. This must change. And it can. In this book, respected software architec