web server - Borland Technical Publications

Container-Managed Persistence in Borland Enterprise Server
CASE 2: a bidirectional
one-to-many
relationship.
SPECIAL_INFO
CUSTOMER_NO
Next, we finish the entry by providing its other half, the SpecialInfo
bean. Since this is a mono-directional relationship, we don't need to specify any table
elements. We only need add the following, defining the other half of the relationship
and its source:
SpecialInfo
Here, we have a Customer entity bean with a primary key, CUSTOMER_NO, that is also a
foreign key in an Order entity bean. We want the Borland EJB Container to manage this
relationship. The Customer bean uses a field called “orders” that links a customer to his
orders. The Order bean uses a field called “customers” for linking in the reverse
direction. First, we define the relationship and its source for the first direction: setting up
the mapping for a Customer's orders.
Customer
orders
Then, we add the table references to specify the relationship between the tables. We're
basing this relationship on the CUSTOMER_NO column, which is a primary key for Customer
and a foreign key for Orders:
CUSTOMER
CUSTOMER_NO
ORDER
CUSTOMER_NO
Chapter 15: Entity Beans and Table Mapping for CMP 2.0 137