Home > Articles > Programming > Java

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

5.6 Design Guidelines and Patterns

This chapter contrasts stateless session beans with stateful session beans. We discuss situations where each is the preferable choice for implementing an EJB. To implement the Value List Iterator Pattern, we use a stateful session bean to control a data-intensive stateless session bean.

Value List Iterator Pattern

In situations where an enterprise application requests a large amount of data, the Value List Iterator Pattern eases network load and the resource consumption caused by large data returns. Instead of receiving all the data at once, the client controls the amount by requesting data a page at a time. Furthermore, the client can control how many elements a page contains.

Our implementation of this pattern uses both a stateful bean (MusicIterator EJB) and a stateless bean (MusicPage EJB). The stateful bean keeps track of per-client data: the desired page size and the current location in the data set. It also provides client-friendly routines such as hasMoreElements() and hasPrevi-ousElements() to help with end-of-data and start-of-data boundary conditions.

Why not eliminate the MusicIterator EJB and place the paging state information in another component? If the MusicPage EJB maintains this information, it would have to be stateful. This affects performance, since the EJB container will possibly have to passivate and activate this data. What if we place the paging state information in the JSP web client? Although we can certainly do this, our attempt here is to separate business logic from the presentation layer. A stateful MusicIterator EJB allows other clients to page through the database (such as a stand-alone Java application or another web component). And because the MusicIterator EJB is decoupled from the recording data, activating and passivating the stateful MusicIterator EJB does not require much overhead.

The stateless MusicPage EJB (which the EJB container can assign to various clients as needed) performs the data-intensive job of reading the database. To make database access vendor independent, we use the DAO pattern. Depending on the timing of the client requests, it is possible for a single instance of the MusicPage EJB to service many clients.

Design Guideline

When using a ValueListIterator, pick a page size that is appropriate for network load and transmission speed. Use a large page size with a fast network and a smaller page size for slower networks.

Stateful vs. Stateless Session Beans

We've touched on the major issues in this chapter. If a session bean must keep track of client-specific data, then you should make it a stateful session bean. Remember that a stateful session bean is tied to a single client. Because sharing instances is not possible, stateful session beans can become a resource liability within your system. There are several ways to avoid using stateful session beans.

  • Encapsulate client data into value objects and pass them to methods of a stateless session bean. The downside to this approach is that it puts the burden on the client to keep track of this data. However, if the data is not complicated and doesn't change much, this is a good approach. (We used this tactic with the Loan EJB in Chapter 3. Each method requires the LoanVO value object which the client creates. See Listing 3.2 on page 41.)

  • If you have a session bean that is expensive to create and keep around, you might be able to wrap client-specific functionality into a small, streamlined stateful session bean. This front-end bean can then forward its calls to a stateless session bean that does all the work. This is the approach we use for the stateful MusicIterator EJB as a front end to the stateless MusicPage EJB. With this approach, the EJB container can efficiently manage the stateless, more resource-intensive enterprise bean.

Local Interfaces

Implementing a session or entity bean with local access can potentially improve the performance of an enterprise application. We say potentially, because although local calls are more efficient than corresponding remote calls, EJBs with local access must execute in the same JVM as its clients. In the long run, this restriction might hedge an enterprise application's scalability, since it prohibits the distribution of local clients across machines.

JSP Web Clients

JSP programs seem like quick solutions to provide user input and presentation aspects of an enterprise application. However, you must be careful not to build too much complexity into a JSP client. The example we provide in this chapter is about as complicated as you should get. The goal is to reduce business logic and scriptlet code in JSP files and limit JSP programs to presentation issues.

That said, what other implementation strategies are helpful for creating JSP clients? Pay particular attention to JSP clients that use stateful session beans (such as the example presented in this chapter).

  • A JSP client that instantiates a stateful session bean should not use class-wide variables to hold client-specific state. Instead, the client should use variables declared inside the _jspService() routine (that is, in scriptlet code, not in JSP declarations).

  • A JSP client that instantiates a stateless session bean can use a class-wide variable. These are declared once during the life of a JSP component and can be easily shared among multiple requests.

  • + 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.

Overview


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.

Surveys

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.

Newsletters

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.

Security


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

Children


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

Marketing


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.

Choice/Opt-out


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.

Links


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