Exercise 6.2: Dependent Value Classes in CMP 2.0
by Richard Monson-Haefel, Bill Burke, Sacha Labourey
Enterprise JavaBeans, Fourth Edition
- Enterprise JavaBeans, 4th Edition
- Preface
- I. Lay of the Land
- 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 Remote and Local Client View
- 6. CMP: Basic Persistence
- 7. 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. 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
- Functional Expressions
- EJB 2.1: The ORDER BY Clause
- Problems with EJB QL
- 9. Bean-Managed Persistence
- 10. The Entity-Container Contract
- The Primary Key
- The Callback Methods
- 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
- 11. Session Beans
- The Stateless Session Bean
- The ProcessPayment EJB
- The database table (PAYMENT)
- The remote interface (ProcessPaymentRemote)
- Dependent objects (CreditCardDO and CheckDO classes)
- An application exception (PaymentException)
- The home interface (ProcessPaymentHomeRemote)
- The bean class (ProcessPaymentBean)
- Accessing environment properties (JNDI ENC)
- The ProcessPayment EJB’s deployment descriptor
- Local component interfaces
- The ProcessPayment EJB
- The Life Cycle of a Stateless Session Bean
- The Stateful Session Bean
- Getting Set Up for the TravelAgent EJB
- The TravelAgent EJB
- The remote interface (TravelAgent)
- Dependent object (TicketDO)
- The home interface (TravelAgentHomeRemote)
- Taking a peek at the client view
- TravelAgentBean: The bean class
- JNDI ENC and EJB references
- Remote EJB references in the JNDI ENC
- Local EJB references in the JNDI ENC
- The bookPassage( ) method
- Why use a Reservation entity bean?
- Listing behavior (listAvailableCabins( ))
- The TravelAgent deployment descriptor
- The Life Cycle of a Stateful Session Bean
- The Stateless Session Bean
- 12. Message-Driven Beans
- JMS and Message-Driven Beans
- JMS-Based Message-Driven Beans
- The Life Cycle of a Message-Driven Bean
- Connector-Based Message-Driven Beans
- EJB 2.1: Message Linking
- 13. Timer Service
- 14. EJB 2.1: Web Service Standards
- 15. EJB 2.1 and Web Services
- 16. Transactions
- ACID Transactions
- Declarative Transaction Management
- Isolation and Database Locking
- Nontransactional Beans
- Explicit Transaction Management
- Exceptions and Transactions
- Transactional Stateful Session Beans
- 17. J2EE
- 18. XML Deployment Descriptors
- The ejb-jar File
- The Contents of a Deployment Descriptor
- The Document Headerand Schema Declarations
- The Descriptor’s Body
- Describing Enterprise Beans
- Describing Relationships
- Describing Bean Assembly
- 19. EJB Design in the Real World
- II. JBoss Workbook
- 20. Introduction
- 21. JBoss Installation and Configuration
- 22. Exercises for Chapter 4
- 23. Exercises for Chapter 5
- 24. Exercises for Chapter 6
- 25. Exercises for Chapter 7
- 26. Exercises for Chapter 8
- 27. Exercises for Chapter 9
- 28. Exercises for Chapter 11
- 29. Exercises for Chapter 12
- Exercise 12.1: JMS as a Resource
- Exercise 12.2: The Message-Driven Bean
- 30. Exercises for Chapter 13
- 31. Exercises for Chapter 15
- A. Database Configuration
- Index
- Colophon
The example programs in Exercise 6.2 explore using a dependent value class to combine multiple CMP fields into a single serializable object that can be passed in and out of entity-bean methods.
Perform the following steps:
Open a command prompt or shell terminal and change to the
ex06_2directory created by the extraction processSet the
JAVA_HOMEandJBOSS_HOMEenvironment variables to point to where your JDK and JBoss 4.0 are installed. Examples:Windows: C:workbookex06_2> set JAVA_HOME=C:jdk1.4.2 C:workbookex06_2> set JBOSS_HOME=C:jboss-4.0Unix: $ export JAVA_HOME=/usr/local/jdk1.4.2 $ export JBOSS_HOME=/usr/local/jboss-4.0Add
antto your execution path.
Windows:
C:workbookex06_2> set PATH=..antin;%PATH%
|
Unix:
$ export PATH=../ant/bin:$PATH
|
Perform the build by typing ant.
As in the last exercise, you will see titan.jar
rebuilt, copied to the JBoss deploy directory,
and redeployed by the application server.
There are no new JBoss configuration files or components in this exercise.
The example program, Client_62, shows how the
Name dependent value class is used with the
Customer EJB. The example code is pulled directly from the EJB book
and embellished somewhat to expand on introduced concepts. The EJB
book does a pretty good job of explaining the concepts illustrated in
Client_62, so further explanation of the code is
not needed in this workbook.
The client application uses the new getName( ) and
setName( ) methods of the Customer EJB to
initialize, modify, and display a newly created Customer bean using
the Name dependent value class. This test bean is
then removed from the database before the application finishes.
To run Client_62, invoke the Ant task
run.client_62. Remember to set your
JBOSS_HOME and PATH environment
variables. The output should look something like this:
C:workbookex06_2>ant run.client_62
Buildfile: build.xml
prepare:
compile:
ejbjar:
run.client_62:
[java] 1 = Richard Monson
[java] 1 = Richard Monson-Haefel-
No Comment