A. Database Configuration
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
This appendix describes how to set up database pools for data sources other than the default database embedded in JBoss, Hypersonic SQL. It also shows you how to set up your EJBs to use these database pools. For illustration purposes, we’ve modified Exercise 6.1 to configure and use an Oracle connection pool with JBoss.
To deploy a database connection pool, JBoss requires a datapool configuration file. The configuration file is very simple, yet can be used for almost all standard datapool setups.
The first step is to download the JDBC driver classes for your
database. Copy your database’s
JDBC JAR file to
$JBOSS_HOME/server/default/lib. For example, the
Oracle JDBC class files are contained in
classes12.zip.
The JBoss distribution includes example database connection-pool
files, in the directory
$JBOSS_HOME/docs/examples/jca. The name of each
file ends in -ds.xml. For this exercise,
we’ve copied the oracle-ds.xml
configuration file to exAppendixA/titandb-ds.xml
and modified it accordingly.
To deploy this connection pool, you must copy
titandb-ds.xml to the
$JBOSS_HOME/service/default/deploy directory.
Note that the name of this config file must end with
-ds.xml, or JBoss will not deploy it.
Tip
Database connection pools are among the many things that can be
hot-deployed in JBoss, simply by plopping the pool’s
XML configuration file into the deploy
directory.
Examine some of the configuration parameters this file defines.
<datasources>
<local-tx-datasource>
<jndi-name>OracleDS</jndi-name>The
<jndi-name>
tag identifies the connection pool
within JNDI. You can look up this pool in JNDI with the
java:/OracleDS string. The class of this bound
object is javax.sql.DataSource.
<connection-url
>jdbc:oracle:thin:@localhost:1521:JBOSSDB</connection-url>The
<connection-url>
tag tells the Oracle JDBC driver how to
connect to the database. The URL varies depending on the database you
use, so consult your database JDBC manuals to find out how to obtain
the appropriate address.
<driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
The
<driver-class>
tag tells JBoss and the base JDBC
classes the name of Oracle’s JDBC driver class they
need to instantiate and use.
<user-name>scott</user-name>
<password>tiger</password>
</local-tx-datasource>
</datasources>Finally, the <user-name> and
<password> tags are used when connecting to
the Oracle database.
-
No Comment