- Enterprise JavaBeans, 2nd Edition
- Dedication
- Preface
- 1. Introduction
- 2. Architectural Overview
- 3. Resource Management and the Primary Services
- 4. Developing Your First Enterprise Beans
- Choosing and Setting Up an EJB Server
- Developing an Entity Bean
- Developing a Session Bean
- TravelAgent: The Remote Interface
- TravelAgentHome: The Home Interface
- TravelAgentBean: The Bean Class
- EJB 1.1: TravelAgent Bean’s Deployment Descriptor
- EJB 1.0: The TravelAgent Beans’ Deployment Descriptor
- EJB 1.1: The JAR File
- EJB 1.0: The JAR File
- Deploying the TravelAgent Bean
- Creating a Client Application
- 5. The Client View
- 6. Entity Beans
- Container-Managed Persistence
- Bean-Managed Persistence
- Making the ShipBean a Bean-Managed Entity
- Exception Handling
- EntityContext
- EJB 1.1: EJBContext
- EJB 1.0: EJBContext
- Obtaining a Connection to the Database
- The ejbCreate( ) Method
- The ejbLoad( ) and ejbStore( ) Methods
- The ejbRemove( ) Method
- ejbFind( ) Methods
- EJB 1.1: Deploying the Bean-Managed Ship Bean
- EJB 1.0: Deploying the Bean-Managed Ship Bean
- The Life Cycle of an Entity Bean
- Does Not Exist
- The Pooled State
- The Ready State
- Transitioning from the Pooled state to the Ready State via creation
- Transitioning from the Pooled state to the Ready State via a find method
- Transitioning from the Pooled state to the Ready State via activation
- Transitioning from the Ready State to the Pooled state via passivation
- Transitioning from the Ready State to the Pooled state via removal
- Life in the Ready State
- End of the Life Cycle
- 7. Session Beans
- The Stateless Session Bean
- Downloading the Missing Pieces
- The ProcessPayment Bean
- PAYMENT: The database table
- ProcessPayment: The remote interface
- Dependent classes: The CreditCard and Check classes
- PaymentException: An application exception
- ProcessPaymentHome: The home interface
- ProcessPaymentBean: The bean class
- EJB 1.1: Accessing environment properties
- EJB 1.1: EJBContext
- EJB 1.1: The ProcessPayment bean’s deployment descriptor
- EJB 1.0: The ProcessPayment bean’s deployment descriptor
- The Life Cycle of a Stateless Session Bean
- The Stateful Session Bean
- The TravelAgent Bean
- TravelAgent: The remote interface
- TravelAgentHome: The home interface
- Taking a peek at the client view
- TravelAgentBean: The bean class
- Why use a Reservation entity bean?
- listAvailableCabins( ): Listing behavior
- EJB 1.1: The TravelAgent deployment descriptor
- EJB 1.0: The TravelAgent deployment descriptor
- The TravelAgent Bean
- The Life Cycle of a Stateful Session Bean
- The Stateless Session Bean
- 8. Transactions
- ACID Transactions
- Declarative Transaction Management
- Isolation and Database Locking
- Non-Transactional Beans
- Explicit Transaction Management
- EJB 1.1: Exceptions and Transactions
- EJB 1.0: Exceptions and Transactions
- Transactional Stateful Session Beans
- 9. Design Strategies
- Hash Codes in Compound Primary Keys
- Passing Objects by Value
- Improved Performance with Session Beans
- Bean Adapters
- Implementing a Common Interface
- Entity Beans Without Create Methods
- Entity Bean Relationships
- Object-to-Relational Mapping Tools
- When Entity Beans Are Not an Option
- Avoid Chaining Stateful Session Beans
- 10. XML Deployment Descriptors
- 11. Java 2, Enterprise Edition
- A. The Enterprise JavaBeans API
- B. State and Sequence Diagrams
- C. EJB Vendors
- D. New Features in EJB 1.1
- Index
- Colophon
Sun Microsystems’ definition of Enterprise JavaBeans is:
The Enterprise JavaBeans architecture is a component architecture for the development and deployment of component-based distributed business applications. Applications written using the Enterprise JavaBeans architecture are scalable, transactional, and multi-user secure. These applications may be written once, and then deployed on any server platform that supports the Enterprise JavaBeans specification.[2]
Wow! Now that’s a mouthful and not atypical of how Sun defines many of its Java technologies—have you ever read the definition of the Java language itself? It’s about twice as long. This book offers a shorter definition:
Enterprise JavaBeans is a standard server-side component model for component transaction monitors.
We have already set the stage for this definition by briefly defining the terms distributed objects, server-side components, and component transaction monitors. To provide you with a complete and solid foundation for learning about Enterprise JavaBeans, this chapter will now expand on these definitions.
[2] Sun Microsystems’ Enterprise JavaBeans™ Specification, v1.1, Copyright 1999 by Sun Microsystems, Inc.
-
No Comment