Home > Articles > Programming > Java

Transitioning to EJB 2.0

📄 Contents

  1. Stepping Up to EJB 2.0
  2. Getting Started
  3. Conclusion
Although the Enterprise JavaBeans (EJB) 2.0 Specification was finalized in August 2001 and several of the leading application servers support it, many EJB developers are still working with applications based on the 1.1 specification. Depending on your application, some of the EJB 2.0 changes bring with them a significant amount of rework. However, several steps can be taken at a relatively small cost to improve both the portability and the maintainability of an existing application. This article discusses some of the simplest ways that a developer using an EJB 2.0-capable server can begin making the move to the latest and greatest that EJB has to offer.
Portions of this article are derived from Special Edition Using Enterprise JavaBeans 2.0 (Que, 2001), by Chuck Cavaness and Brian Keeton.
Like this article? We recommend

Although the Enterprise JavaBeans (EJB) 2.0 Specification was finalized in August 2001 and several of the leading application servers support it, many EJB developers are still working with applications based on the 1.1 specification. With the lengthy review process that took place for the latest specification, most developers are at least aware of the advantages EJB 2.0 offers. However, the business case for upgrading an existing application can be hard to justify, especially during an economic downturn.

Depending on your application, it's true that some of the EJB 2.0 changes bring with them a significant amount of rework. However, this doesn't hold true for all of EJB 2.0. Several steps can be taken at a relatively small cost to improve both the portability and the maintainability of an existing application. This article discusses some of the simplest ways that a developer using an EJB 2.0–capable server can begin making the move to the latest and greatest that EJB has to offer.

Stepping Up to EJB 2.0

To set the stage, we'll start with a quick summary of the major changes. The most visible of these is the introduction of a third bean type, the message-driven bean. This addition allows an EJB application to make use of the Java Message Service (JMS) in a standard way. You can implement business logic using a message-driven bean that is executed asynchronously in response to messages sent to a JMS queue or topic. These messages can be sent by an external client of your application or another component within it. Under earlier EJB versions, the use of asynchronous messaging within your applications had to take place outside the EJB framework and often depended on vendor-specific capabilities.

EJB 2.0 has also changed how method calls between beans deployed within the same container can be executed. Under EJB 1.1, all clients of session and entity beans are viewed as remote clients. A remote client creates or locates an EJB object by calling a method on the bean's home interface. The client then invokes business logic by calling the remote interface. The EJB container intercedes on all calls to these interfaces to provide necessary services such as security and support for transactions. This approach leads to location independence, meaning that a client application can be coded and executed the same regardless of whether an EJB that it depends on is deployed on the same machine or somewhere else on the network. Location independence requires that method calls always follow pass-by-value semantics. This means that method arguments and return values are marshaled back and forth even when the client is another EJB instance running in the same JVM. Some application servers include optimizations to reduce this overhead, but there's no standard across implementations. Because of this drawback, some of the EJB design patterns first adopted were aimed at reducing the number of calls made from session beans to entity beans.

To improve the performance of calls between enterprise beans, EJB 2.0 introduced support for local clients in addition to remote clients. If a session or entity bean supports other enterprise beans deployed in the same container as clients, those beans can be treated quite differently than other callers. Instead of the remote and home interfaces used by remote clients, local clients interact with a bean through its local and local home interfaces. Calls made through these interfaces use pass-by-reference semantics and avoid the marshalling and other overhead of remote calls. Local clients give up location independence and are tightly coupled to the beans that they access, but the performance advantages make up for these limitations whenever remote client access isn't needed.

Besides adding local home interfaces, EJB 2.0 added another type of method to an entity bean's home. EJB 1.1 home interfaces declare only the methods that create new instances of a bean and locate existing entity objects—you declare all business methods for a bean in its remote interface. Because static methods aren't allowed in an EJB, you can execute a business method only by invoking it on a particular object through its remote interface. If you need to implement a business method for an entity bean class that doesn't depend on any particular entity instance (or one that depends on more than one of them), using a session bean method is the option most widely used in EJB 1.1. Static methods are still prohibited by EJB 2.0, but you can now implement business methods within a bean class that are independent of any particular instance. You declare these methods, known as home methods, in the home or local home interface. When you call a home method, the container selects an available instance of the bean class from the pool that it manages and invokes the method on that instance. Similar to static methods, a home method cannot reference any fields of the instance used to invoke it.

If you use entity beans with container-managed persistence (CMP), the 2.0 specification introduces a fundamentally different implementation approach. The bean classes that you write for a CMP entity bean are now abstract classes that define their fields through a series of abstract get and set method declarations. Instead of including any actual field declarations, your classes identify their fields using only their method declarations. These declarations form part of what is known as the abstract persistence schema for a CMP bean. It's the responsibility of the container to generate a concrete bean class based on the fields declared by your get and set methods and the relationships that you define in the deployment descriptor. As part of this, the container now manages relationships between entity beans as a standard capability. To address another portability issue, finder methods are defined using a standard syntax known as the EJB Query Language (EJB QL). You can port finder method queries defined with EJB QL to any EJB 2.0 container without having to modify them.

EJB 2.0 includes a few other changes, but those mentioned so far are the only ones we need to look at for our purposes here. The other enhancements deal primarily with the security role applied to calls made by an EJB and the interoperability of EJBs with J2EE applications deployed in another vendor's application server.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020