Home > Articles > Programming > Java

  • Print
  • + Share This
This chapter is from the book

3.11 Assembly and deployment

In almost all software development exercises, the computers used to develop the software are not the same as the ones that will be used to run it when in service. Unlike most other forms of software development, the format in which EJBs are packaged for transfer from a development system to a production system is standardized: EJBs are packaged into EJB-JAR files, which are in turn packaged into an EAR file. The EJB server is required by the EJB Specification to be able to take a correctly formatted EAR file from any source and install the EJBs it contains. Many products allow EJB-JAR files to be deployed without constructing an EAR file, which is convenient during development. This process, whether applied to EJB-JARs or to EARs, is called deployment.

An EAR file can contain EJBs from a number of different sources, produced by different developers. When these EJBs are combined into a single application, it may be necessary to resolve name mismatches between EJBs and satisfy references to external databases, among other things. This process is called application assembly.

While deployment and assembly are different processes, most vendors allow both to be carried out with the same software tool. Therefore, many developers don’t distinguish sharply between assembly and deployment tools. When we talk of a ‘deployment tool,’ we usually mean something that can do assembly as well. The term ‘assembly’ is also used for the packaging of classes into an EJB and the construction of a deployment descriptor.

During deployment, the vendor’s tools will normally construct the home and remote objects, and the home and remote stubs. The latter should be made accessible for standalone clients.


Having set up the structure and contents on the EJB-JAR file, deployment to the server ought to be a trivial job, whether using scripts, command-line tools, or vendors’ graphical tools. If you modify and recompile the EJB classes, updating the EJB-JAR and redeploying to the server should also be trivial. If it requires more than, say, four mouse clicks or two commands, ask the vendor why this is. If you don’t get a straight answer, ask for your money back. Deploying an EJB is not rocket science, and should not present a problem for a modern software tool.

3.11.1 The EJB-JAR file

An EJB file is simply a Java JAR archive, with a particular structure. The class files are organized in the JAR to reflect the package hierarchy, as usual, while deployment descriptors are placed in a directory called META-INF. If we have an EJB called ‘BankTeller,’ for example, whose classes are in the package com.acme.ejb and have been named according to the convention described above, then the EJB-JAR will have the following format:

  (other descriptors) 

Note that the EJB Specification allows EJB server vendors to provide facilities to configure their products in ways that are not mandated (or, at least, does not forbid this). For example, the EJB Specification has nothing to say about load sharing, but this is a key feature of all commercial products. This kind of information cannot be placed into the standard deployment descriptor ejb-jar.xml, as the format of this file is strictly defined. So most vendors expect additional deployment descriptors. Ideally, the absence of these additional descriptors should not prevent the application from operating, although its performance may not be optimal. In practice, however, many vendors’ products simply don’t work at all without this extra information. This is one of the reasons why the cross-platform compatibility promised by EJB technology is not as easy to realize as may be hoped.

3.11.2 The EAR file

The EAR file contains a number of EJB-JAR files, along with WAR files that contain Web components (servlets, JSP pages, etc).

If the EJB-JAR file described above was called bankteller.jar, and this was the only EJB-JAR in the application, then the EAR file would have the following structure.

    (other descriptors) 

The deployment descriptor application.xml contains the following information:

  • the display name of the application;

  • a list of the EJB-JAR and WAR files that are to be deployed;

  • application-wide security roles (see Chapter 16).

Again, the EJB Specification allows the vendor to use deployment descriptors in addition to the standard one to convey product-specific configuration information. It is also conventional to include in the EAR file any additional class libraries that the application requires (that are not part of the EJBs).

3.11.3 Dynamic proxy and stub generation

It should be apparent by now that the home object and the EJB object/local object play key roles in EJB technology. Because these objects are proxies for the EJB, the methods they implement will usually depend on the methods in the EJB they serve. Thus, it is not practical for the EJB server to use general-purpose home and EJB objects. These objects will usually be generated dynamically at deployment time. In addition, the home stub and remote stub will also need to be generated, along with skeletons, if they are used.

The strategy used by most vendors is for their deployment tool to inspect the factory interface and business method interface of each EJB, using Java reflection, and construct the home objects, EJB object, EJB local object, and stubs as Java source files in a temporary directory. These source files are then compiled, and the classes inserted into the appropriate place in the server’s CLASSPATH.

The stubs are required by clients of the EJBs, so these must be made available to install on the client. The usual approach is for the deployment tool to package these up into a JAR file (called, for example, clientstubs.jar) and allow the deployer to select where they should be saved. Although Java RMI supports automatic stub downloading (see page 36), this technique is rarely used by EJB products, and it is normal to distribute the stubs along with the other client code.

  • + Share This
  • 🔖 Save To Your Account

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