web server - Borland Technical Publications

Container-Managed Persistence in Borland Enterprise Server
CASE 1: A
development
environment without
existing database
tables using either
JDataStore or
Cloudscape databases.
CASE 2: A deployment
environment with (or
without) existing
database tables using
supported databases.
In this case, the Borland CMP engine creates tables automatically, assuming that the
entity bean name is the same as the desired table name. You need only provide the
bean's name and its associated datasource as a property:
CustomerEJB
ejb.datasource
serial://ds/myDatasource
The Borland CMP engine will automatically create tables in this datasource based on
the bean's name and fields.
In this case, you need to supply information on the tables to which the entities map.
You'll provide a table name in the portion of the descriptor, and some
properties in the portion:
CustomerEJB
CUSTOMER
.
.
CUSTOMER
datasource
serial://ds/myDatasource
Note that the datasource property is called datasource when specified in the
element and ejb.datasource when in the element. If you are using
a database other than JDataStore or Cloudscape and would like to have the Borland
CMP engine automatically create this table, add the following XML to the
element:
.
.
CUSTOMER
create-tables
True
Basic Mapping of CMP fields to columns
Basic field mapping is accomplished using the element in the ejbborland.xml
deployment descriptor. In this element, you specify a field name and a
corresponding column to which it maps. Consider the following XML for an entity bean
called LineItem, which maps two fields, orderNumber and line, to two columns,
ORDER_NUMBER and LINE:
LineItem
orderNumber
Chapter 15: Entity Beans and Table Mapping for CMP 2.0 133