Container-managed relations for the
21st century
Tutorial Details:
Container-managed relations for the 21st century
Container-managed relations for the 21st century
By: By Allen Fogleson
EJB 2.0's new relationship facilities assist developers in rapid deployment
ava developers often create complex relationships when they program applications to solve real-world business problems. Therefore, it was no surprise that when programmers began developing enterprise applications using Enterprise JavaBeans (EJB), they continued to describe their business models with complex relationships. In the original specification, EJBs, however, made such complex relationships more difficult because developers had little control over when an EJB was activated or passivated. In response, developers often wrote complex logic to ensure object persistence within these relationships.
Luckily, the EJB specification developers, recognizing the problem, added container-managed relationships (CMR) in EJB 2.0.
What are these relationships? How do you describe them? How do you encode them in your Java classes? In this article I answer those questions and others.
Note: I assume you understand Java and EJB. Although I give a CMP 2 (container-managed persistence) overview, you won't find an exhaustive CMP tutorial here. See Resources for more articles on EJB and CMP.
Also note: You can download this article's code examples from Resources .
CMP 2 overview
Before you can understand EJB relationships, you must first understand how EJBs work. How are their persistent fields defined? How do you define the relationships? What are the relationships' return objects?
The EJB 1.0 and 1.1 specifications identified container-managed fields by placing attributes in the bean, then described the fields in the deployment descriptor. Although other entity beans could reside within the parent entity bean, the container did not automatically handle their persistence or loading. The bean developer, therefore, had to write additional code, normally in the ejbCreate() , ejbActivate() , and ejbPassivate() methods to handle these additional entity beans. The developer, as his only alternative, could define entity beans using bean-managed persistence.
The EJB 2.0 specification changed the situation dramatically. Among the specification's many changes, container-managed fields now no longer have attributes to identify them within the bean; instead they have abstract getters and setters to identify them. Using the getters and setters, you can now also include other entity beans. The getters' return types depend upon the relationships type. If a single child-bean instance returns, the instance is the child bean's local interface. In contrast, if multiple child-bean instances return, the instances are a java.util.Collection or a java.util.Set . The bean developer can then describe the relationship, defined within the deployment descriptor's relationship tag, in the EJB's deployment descriptor. Here's an example:
...
User-Demographics
User-Demographics
One
Users
demographics
Demographics-belongs-to-Users
One
Demographics
...
The example above defines a user bean with a one-to-one, unidirectional relationship to a demographics bean. Let's further examine each XML tag in the deployment descriptor.
The relationships tag tells the container you describe the relationships of the beans contained in this deployment. Each relationship starts with the ejb-relation tag. The ejb-relation-name tag is a human-readable description of the relationship. The ejb-relationship-role tags, of which there are two in each ejb-relation , describe each entity bean's role in this relationship. Each ejb-relationship-role tag contains a human-readable ejb-relationship-role-name tag and describes that bean's role in the relationship. The multiplicity tag describes whether the bean is on the relationship's one or many side. The relationship-role source contains an ejb-name tag, which is the entity bean that participates in the relationship. The ejb-name tag must match one of the EJBs defined in the EJB jar file.
The cmr-field tag is optional. If the described bean lacks a CMR field, it will not be included as demonstrated in the second ejb-relationship-role tag above. However, you must have the cmr-field tag for beans that have a CMR field. The text within the tag contains the cmr-field-name tag describing the CMR field to use in the relationship. Finally, the cascade-delete tag, included in the bean that is the relationship's child, tells the container that if the relationship's parent is deleted, the parent's children should also be deleted.
Relationships overview
The new EJB 2.0 persistence scheme can model eight relationships:
One-to-one unidirectional: The parent bean references one child entity-bean instance. A customer with an address serves as a classic example: customers have meaning to us, but addresses without customers mean little.
One-to-one bidirectional: Both the parent and child beans reference each other. A classic example of this relationship: a customer and a credit card. Given a customer, you need to find his credit card to charge him for a purchase. The accounting department might also need to look up a customer based upon his credit card information.
One-to-many unidirectional: In this relationship, the parent entity bean references many child entity beans, and the child entity beans mean little without the parent. Example: a customer and her associated phone numbers. Knowing a customer, you want to find her telephone numbers; however, you would rarely need to find a customer by knowing a telephone number.
One-to-many bidirectional: Each bean in the relationship references every other bean. The parent bean has many child beans, and each child bean references its parent. As an example, think of a customer and his orders. A customer can have many orders, either pending or complete, and a shipping department might wish to find out to which customer a particular order belongs.
Many-to-one unidirectional: Many parent entity beans reference a single child entity bean. However, the child entity bean does not refer back to the parents. Airline reservations serve as a classic example. Although a flight may occur multiple times, reservations pertain to a single flight. From the customer's view, you just want to know the given reservation's flight information.
Many-to-one bidirectional: Although you can easily model many-to-one bidirectional relationships under the persistence scheme, they are not really unique relationships because they are identical to one-to-many bidirectional relationships.
Many-to-many unidirectional: Many parent beans reference many child beans. The child beans either mean nothing without the parent, or you don't need to look up a parent bean based on a child bean. Expanding on the airline reservation example, not all reservations occur with direct flights. A single reservation may include multiple flights; moreover, many reservations may exist for the same flight. Now from our customer's view, you want to know all the flights in the reservation.
Many-to-many bidirectional: Many parent beans reference many child beans, which likewise reference many parent beans. An event schedule illustrating the relationship of events and locations serves as an example: many events occur in many locations. Given an event, you may want to find its locations. Given a location, you may also wish to find all the events occurring there.
From the list above, you see three major relationship types: one-to-one, one-to-many, and many-to-many. We will explore each in more detail. First, however, let's explore how the EJB 2.0 specification handles such relationships.
Local interfaces
As previously mentioned, the entity bean models each relationship type using abstract assessors. The return type is either a local interface or a local interface collection. Although local interfaces are not unique to entity beans, their use in constructing relationships does restrict their usefulness. Since relationships use local interfaces that can work only within the same VM, only relationships within a single VM can occur. Therefore, you cannot create relationships with other distributed entity beans. Although that restriction hinders many possibilities, it offers one large advantage: local interfaces are extremely fast. Because a remote call's overhead no longer exists, local interface calls act just like other local method calls to a regular Java class.
One-to-one relationships
Now that you understand EJB relationship basics, let's model your first relationship. For simplicity's sake, start with an easy one-to-one relationship: the customer and address relationship. Because in its simplest sense, the customer address relationship is a one-to-one unidirectional relationship, you model it with one customer bean and one address bean. I keep the entity beans simple to concentrate on defining the relationship.
Begin by creating the abstract class defining the customer bean. Although the entity beans presented would work, I've simplified them to demonstrate how the relationships work. In a real system, you would not create entity beans with such primary keys:
package relationships;
import javax.ejb.*;
import java.math.*;
import relationship.*;
public abstract class CustomerBean implements EntityBean {
// The primary key
public
Read
Tutorial at: Click here to view the tutorial
Rate Tutorial: Container-managed relations for the
21st century
View Tutorial: Container-managed relations for the
21st century
Related
Tutorials:
|
Displaying 1 - 36 of about 36 Related Tutorials.
|
 History of Business Intelligence
;
THE 20th AND 21st CENTURY are known as the information and technology (IT) age where
|
Jobs at Rose India
the technical assistance of the growing business communities of 21st century
|
General benefits of a GPS vehicle tracking technology
th and 21 st century. Whether you are an individual worried by the safety of your
|
Open Source Excel
in the 21st century
workplace .
|
Business Intelligence
;
History
of Business Intelligence
The 20th and 21st century are known
|
Open Source Business Model
not generate stable and scalable revenue
streams. In actuality, in the 21st century web technology market, it is the open source company that has the greatest
|
mediniQVT
implements OMG's QVT Relations
specification in a powerful QVT engine. The standard... in the
textual concrete syntax of the Relations language
Trace management
|
Programming - World Peace
Department. I wouldn't be surprised if the public relations
gurus eventually change
|
Introduction To Enterprise Java Bean(EJB). WebLogic 6.0 Tutorial.
Writing Entity Bean with
Container Managed Persistence... Container such as
WebLogic Server 6.0. We will use WebLogic 6.0 Server... Managed Persistence
Deploying Entity
|
Hibernate Training
with Hibernate
JTA
Container Managed
|
Relational Database Concepts
of objects or relations,.
Operators that act on the objects or relations.
Data integrity methods.
To design
|
Blogger
relations among people where they can share ideas, make friends etc. Sounds good hnn
|
GPS and it?s Competitors
of this twenty first century. Though global positioning system is free for civilian use
|
EJB Books
, such as container-managed persistence, and security and transaction management... an entity bean with container managed persistence, you let Resin-CMP generate...
servers. Enterprise JavaBeans (EJB) are a container-based component
|
J2EE interview questions page1
: container managed persistence(CMP) and bean managed persistence(BMP)
... container type and one component deployment descriptor of that type.
... container.
Session Bean
--represents a workflow on behalf of a client
--one
|
What is a blog?
as you can imagine. These blog communities have emerged to form relations among
|
Web 2.0 Model
dynamic and returning custom results to users. With
the evolution of new century
|
Open Source Institute
projects, ranging from software projects
to public relations
|
Database books Page7
. In early relational systems, tables were called relations. A relational database
|
Database books Page10
called relations. A relational database consists of a collection of tables
|
VoIP Advantages
intact the century-old public-switched telephone network they employ, and it left
|
Struts integration with EJB in JBOSS3.2
of Entity Beans are CMP (Container Managed Persistence), BMP
(Bean.... Typical services provided by the EJB Container are as follows... as function bean called in RMI-IIOP style from Enterprise container. Two types
|
Struts integration with EJB in WEBLOGIC7
types of Entity Beans are CMP (Container Managed Persistence), BMP (Bean Managed... Enterprise-level services. Typical services provided by the EJB Container... container. Two types of session bean are stateless session bean, stateful session bean
|
Open Source POS
, customer relations and supply chain management
|
MySQL Download
speed and flexibility. The tables are linked by defined relations making it possible
|
GPS
st century. Whether you are an
individual worried by the safety of your... or other cargo container. So GPS is used by people for navigation
in vehicles...
technology of this twenty first century. Though global positioning system
|
Open Source Books
: this eighteenth-century information superhighway was meant for such serious
|
Open Source CRM
is a new customer relations management (CRM) product from TechWhale, a Tampa, Fla
|
Technology Articles/FAQs
;
History
of Business Intelligence
The 20 th and 21 st century
|
Technology Articles/FAQs
;
History
of Business Intelligence
The 20 th and 21 st century
|
Open Source ERP
management (CRM), partner relations management (PRM), supply chain management (SCM
|
Open Source Intelligence
Committees on Foreign Relations and Foreign Policy out of Carnegie are three.... In particular, intelligence-gathering services can no longer be managed without
|
VoIP Solution
" (Net2Phone, 8x8) competitors. Vonage and its public relations firm want to double
|
IBM Open Source
when attacked.
However, SCO's public relations (PR) department has had... W-13 (formerly managed by MISER). IBM donated new desktop computers, a server
|
Modeling
;
mediniQVT
medini QVT implements OMG's QVT Relations specification
|
Misc.Online Books
: Equivalence relations, injective, surjective, and bijective functions, product of sets... and local files can all be viewed, edited, and managed in the same way; it has
|
|
|
|
