Home > Articles > Programming > Java

Streamline Your Java Web Applications Using Java Server Faces and Managed Beans

Jesse Smith shows you how you to use Enterprise Java Beans as your managed beans behind Java Service Faces to remove at least one integration layer in your application, making your application architecture much easier to follow and more adaptable.
Like this article? We recommend

Many Java programmers have worked with or used Java Beans in their web applications. It has become a timely art, but since the introduction of web services it has slowly faded away. The strength of Java Beans is their capability to manage complex transaction states while providing an easy interface for hiding the class implementation. But most of all, Enterprise Java Beans (EJBs) were designed for distributed components to work across different servlet containers.

It was a good idea, but expensive in terms of remote invocation calls between Java components across the network, and really didn't take off like its successor, web services.

A lot of the web service frameworks took ideas from EJB frameworks, especially for providing remote method access across disparate networks. The strength of web services is that these components can reside on any system and communicate with other components on any other systems, much like EJBs. You could probably say EJBs were primitive web services for only Java-based components and containers. Now, with web services, you can communicate across language boundaries that include components from multiple languages that reside in applications on different web servers.

EJBs have since evolved more or less into POJOs (Plain Old Java Objects) that have removed the need for multiple interface types. With Java 6, you can use Java Server Faces (JSF) 1.2 and EJB 3.1 managed beans to streamline your applications by reducing the number of steps needed to handle requests.

Managed beans in EJB 3.1 are used as the "backing beans" behind JSF events and no longer require interfaces along with handling their own persistence data. EJB 3.1 introduces the concept of a no-interface view, consisting of a variation of the Local view, which exposes all public methods of a bean class. Session Beans are no longer required to implement any interface anymore. The EJB container provides an implementation of a reference to a no-interface view, which allows the client to invoke any public method on the bean, and ensuring that transaction, security, and interception behave as defined.

EJBs are commonly used with Struts, but now with Java Service Faces (JSF), which was built on Struts, you can make your application's Presentation layer much more effective than what Struts provided. JSF uses an event driven model for the Presentation layer (JSPs) that easily raise and handle events with managed beans. Think of JSF as Java Swing[md]but for web applications.

In this article, I will show you how you can remove at least one integration layer in your application, making your application architecture much easier to follow and more adaptable by using EJBs as your managed beans behind Java Service Faces.

Java Application Layers

Most Java programmers have used Data Transfer (DTs) and View Objects (VOs) in their EJB applications. Often, just to get from Presentation layer to your Enterprise Information System (EIS) layer that contains your back-end storage, requires going through some hoops.

For example, using the three-tier model, view, controller architecture for large Java applications typically goes like this:

  1. User requests a JSP.
  2. JSP calls a servlet (front controller in the model, view, control architecture).
  3. Servlet directs request to a Java Action class.
  4. Java Action class calls a Delegate method.
  5. Delegate method calls an EJB interface.
  6. EJB goes to the database or calls other EJBs to collect information required by request.
  7. EJB passes information back in a VO object.
  8. VO object populates a form bean.
  9. Servlet routes response to appropriate JSP on success/failure.

Whew! Even in a nutshell, that's a lot of hoops to go through for one request, even if you're using Entity (Persistence) Beans to interact with the database.

Steps 1, 2, and 3 involve the application's Presentation layer. Steps 4 and 5 involve the Business Logic layer. Steps 6 and 7 involve binding the Business Logic layer to the database layer (Web and Persistent tiers of the EJB container). And finally, steps 8 and 9 come full circle back to the Presentation layer with the response.

What if I told you that we can get rid of four of these steps and yet still maintain a solid model, view, controller architecture? You're in luck, because with Java Server Faces and managed beans, we can do just that.

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