Home > Articles > Programming > Java

Enterprise JavaBeans™ in Context

📄 Contents

  1. Enterprise JavaBeans: what are they, and what do they do?
  2. EJBs in the enterprise
  3. Why use EJBs?
  4. The EJB philosophy
  5. EJB roles
  6. EJB products
  7. Summary
What are Enterprise JavaBeans™ (EJBs) and what can they do for you? Explore why you should jump on the EJB bandwagon, the EJB philosophy, EJB roles and its corresponding products.
This chapter is from the book

This introductory chapter describes the goals and requirements of EJB technology and what you—the developer—can expect to gain by using it. It explains how EJBs t into other distributed programming paradigms (like CORBA), and into the wider 'J2EE' model of application development. The chapter includes an outline of the other services that a J2EE-compliant application server is expected to provide and which EJBs can use (e.g., Java-Mail, JMS). There is a brief discussion of the development philosophy that underlies the EJB Specication, including the roles of the developer, assembler, and deployer, and how the EJB model—appropriately used—can enhance code reuse and improve reliability.

1.1 Enterprise JavaBeans: what are they, and what do they do?

Let's start by examining the answer to this question as provided by the most authoritative source, the EJB Specification itself:

"The Enterprise JavaBeans architecture is a component architecture for the development and deployment of component-based distributed business applications. Applications written using the Enterprise JavaBeans architecture are scalable, transactional, and multi-user secure. These applications may be written once, and then deployed on any server platform that supports the Enterprise JavaBeans specification."

This definition makes a number of important assertions, which are worth considering in more detail.

"...a component architecture..." The distinction between 'component-based' and 'object-oriented' development is not a strict one, and you will see EJBs referred to as 'distributed components' and 'distributed objects.' I take the term 'component' in EJB technology to mean a piece of software that is self-contained, has well-defined functionality, and fits into some kind of application framework. It is this latter point that probably makes the term 'component' more applicable than 'object' in EJB technology.

The application framework is exemplified by the EJB container, a concept about which we will have much more to say later. EJBs depend for their very existence on their container; it regulates all aspects of their lives, including their communication with other EJBs [EJB2.0 6.2]. This is not the restriction that it first appears, because the use of the container has profound advantages, as we shall see.

EJBs can be viewed as simple objects: They expose methods, and these methods can be called. Like ordinary objects, the methods take arguments and can return values. Unlike ordinary objects, EJBs can be distributed across different hosts, and the architecture takes care of the communication. When a client makes a method call on an EJB, it is in fact making that call on the container, which acts as a proxy, as we shall see.

"...distributed business applications..." What is a 'business application' ? This is a very broad term, but we can identify certain characteristics that most business applications will exhibit. First, there is a reliance on data, often in volume, and with strict measures to protect the integrity of that data. Most business applications make use of relational databases. Second, many business applications have large numbers of users, often geographically distant from the application host. Third, business applications often integrate systems of different types, from different vendors. Some of these systems will be 'legacy' systems—that is, based on obsolete software and protocols, but needing to be retained. EJBs can make use of messaging services, connectors, and other techniques for access to legacy systems. The EJB infrastructure has interoperability as one of its core requirements [EJB2.0 19.2]. Applications are 'distributed' when components can be hosted on different servers. The ability to distribute components has important implications for fault tolerance and load sharing, as we shall see.

It is worth pointing out at this point that, under EJB 2.0, not all EJBs have to be capable of distribution. The developer is at liberty to author EJBs such that they are only accessible to calls from other EJBs in the same JVM. This makes access more efficient at the expense of limiting load balancing and fault tolerance. We will have much more to say about this issue later.

"...scalable..." An application is scalable if the system that hosts it can be expanded or upgraded to support a higher client load, without significant modification to the software. Scalable does not necessarily mean 'high performance,' despite a common belief that this is the case. EJB applications support scalability because they lend themselves to distribution; they support high performance because they allow the sharing of resources and minimize overheads, as we shall see.

" transactional..." Where business applications are datacentric, the integrity of the data is of paramount importance. This means that access to the databases, and often to other resources, will be transactional—that is, consist of operations that must succeed or fail as a group. We will have much more to say about this issue in Chapter 9, as transaction management is a key feature of the EJB infrastructure, particularly in a distributed environment [EJB2.0 19.6].

" multi-user secure..." Business applications will need to be able to identify their users, and allow access to the data only to defined users. Information about which users are allowed which operations is often not part of the application, but stored in some sort of user database (e.g., an LDAP directory server). Security is an integrated part of the EJB framework, as described in Chapter 16.

"...written once, and deployed on any server..." With care, EJB applications can be made quite portable (but see below). The use of the Java language ensures portability not merely at the source-code level, but at the binary level. This makes it appealing for vendors to author EJB components that are general-purpose and can be integrated into other applications. A requirement to distribute source code would discourage this. Provided that the EJB author is careful to follow the Specification, the interaction between the EJB and its container should not depend on the container vendor. The EJB architecture is designed to support the use and integration of components from different vendors, by such means as using a standard (XML-based) configuration scheme for components.

In summary, EJBs are Java3 software components that run in a framework that supports distribution, load sharing, fault tolerance, security, and transaction management. To their clients they 'look like' ordinary Java objects, and can be used similarly.

In a more pragmatic sense, EJBs are components built from Java program classes and interfaces. In particular, each EJB has at least one class, which provides the application functionality, and, where direct interaction by clients is allowed, two or four interfaces, which specify which methods are to be exposed to clients. These Java elements are packaged into a standard Java JAR file along with a deployment descriptor, an XML file that provides configuration information to the server. Each JAR file can contain one or more EJBs. In practice, we tend to use graphical tools for building the JAR and XML files.

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