- Enterprise JavaBeans, 3rd 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
- 5. The Client View
- 6. EJB 2.0 CMP: Basic Persistence
- 7. EJB 2.0 CMP: Entity Relationships
- The Seven Relationship Types
- Abstract Persistence Schema
- Database Modeling
- One-to-One Unidirectional Relationship
- One-to-One Bidirectional Relationship
- One-to-Many Unidirectional Relationship
- The Cruise, Ship, and Reservation EJBs
- Many-to-One Unidirectional Relationship
- One-to-Many Bidirectional Relationship
- Many-to-Many Bidirectional Relationship
- Many-to-Many Unidirectional Relationship
- Co-location and the Deployment Descriptor
- Cascade Delete and Remove
- The Seven Relationship Types
- 8. EJB 2.0 CMP: EJB QL
- Declaring EJB QL
- The Query Methods
- EJB QL Examples
- Simple Queries
- Simple Queries with Paths
- The IN Operator
- Using DISTINCT
- The WHERE Clause and Literals
- The WHERE Clause and Input Parameters
- The WHERE Clause and Operator Precedence
- The WHERE Clause and CDATA Sections
- The WHERE Clause and Arithmetic Operators
- The WHERE Clause and Logical Operators
- The WHERE Clause and Comparison Symbols
- The WHERE Clause and Equality Semantics
- The WHERE Clause and BETWEEN
- The WHERE Clause and IN
- The WHERE Clause and IS NULL
- The WHERE Clause and IS EMPTY
- The WHERE Clause and MEMBER OF
- The WHERE Clause and LIKE
- The WHERE Clause and Functional Expressions
- Problems with EJB QL
- 9. EJB 1.1 CMP
- 10. Bean-Managed Persistence
- 11. The Entity-Container Contract
- The Primary Key
- The Callback Methods
- EJB 2.0: ejbHome( )
- EntityContext
- 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 query 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
- 12. Session Beans
- The Stateless Session Bean
- The ProcessPayment EJB
- PAYMENT: The database table
- ProcessPaymentRemote: The remote interface
- Dependent objects: The CreditCardDO and CheckDO classes
- PaymentException: An application exception
- ProcessPaymentHomeRemote: The home interface
- ProcessPaymentBean: The bean class
- JNDI ENC: Accessing environment properties
- EJBContext
- The ProcessPayment EJB’s deployment descriptor
- EJB 2.0: Local component interfaces
- The ProcessPayment EJB
- The Life Cycle of a Stateless Session Bean
- The Stateful Session Bean
- EJB 2.0: Getting Set Up for the TravelAgent EJB
- EJB 1.1: Getting Set Up for the TravelAgent EJB
- The TravelAgent EJB
- TravelAgent: The remote interface
- Dependent object: TicketDO
- TravelAgentHomeRemote: The home interface
- Taking a peek at the client view
- TravelAgentBean: The bean class
- JNDI ENC and EJB references
- The bookPassage( ) method
- Why use a Reservation entity bean?
- listAvailableCabins( ): Listing behavior
- EJB 2.0: The TravelAgent deployment descriptor
- EJB 1.1: The TravelAgent deployment descriptor
- The Life Cycle of a Stateful Session Bean
- The Stateless Session Bean
- 13. Message-Driven Beans
- JMS as a Resource
- Message-Driven Beans
- The ReservationProcessor EJB
- The ReservationProcessorBean Class
- MessageDrivenBean interface
- MessageDrivenContext
- MessageListener interface
- The onMessage( ) method: Workflow and integration for B2B
- Sending messages from a message-driven bean
- XML deployment descriptor
- <message-selector>
- Message selector examples
- <acknowledge-mode>
- <message-driven-destination>
- The ReservationProcessor clients
- The Life Cycle of a Message-Driven Bean
- The ReservationProcessor EJB
- 14. Transactions
- ACID Transactions
- Declarative Transaction Management
- Isolation and Database Locking
- Nontransactional Beans
- Explicit Transaction Management
- Exceptions and Transactions
- Transactional Stateful Session Beans
- 15. 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
- EJB 1.1: Object-to-Relational Mapping Tools
- Avoid Emulating Entity Beans with Session Beans
- Direct Database Access from Session Beans
- Avoid Chaining Stateful Session Beans
- 16. XML Deployment Descriptors
- What Is an XML Deployment Descriptor?
- The Contents of a Deployment Descriptor
- The Document Header
- The Descriptor’s Body
- Describing Enterprise Beans
- EJB 2.0: Describing Relationships
- Describing Bean Assembly
- The ejb-jar File
- 17. Java 2, Enterprise Edition
- A. The Enterprise JavaBeans API
- Package: javax.ejb
- EJB 2.0: AccessLocalException
- CreateException
- DuplicateKeyException
- EJBContext
- EJBException
- EJBHome
- EJB 2.0: EJBLocalHome
- EJB 2.0: EJBLocalObject
- EJBMetaData
- EJBObject
- EnterpriseBean
- EntityBean
- EntityContext
- FinderException
- Handle
- HomeHandle
- EJB 2.0: MessageDrivenBean
- EJB 2.0: MessageDrivenContext
- NoSuchEntityException
- ObjectNotFoundException
- RemoveException
- SessionBean
- SessionContext
- SessionSynchronization
- EJB 2.0: TransactionRequiredLocalException
- EJB 2.0: TransactionRolledbackLocalException
- EJB 2.0: Package: javax.jms
- EJB 2.0: Package: javax.ejb.spi
- Package: javax.ejb
- B. State and Sequence Diagrams
- C. EJB Vendors
- 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.[3]
That’s a mouthful, but it’s 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 of EJB:
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.
If you already have a clear understanding of distributed objects, transaction monitors, CTMs, and asynchronous messaging, feel free to skip the rest of this chapter and move on to Chapter 2.
[3] Sun Microsystems’ Enterprise JavaBeans™ Specification, v2.0, Copyright 2001 by Sun Microsystems, Inc.
-
No Comment