Home > Articles > Programming > Java

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

This chapter is from the book

Up until now, all the bean properties have have been simple types: strings of text or numbers. This feature of the examples that have appeared is not a fundamental restriction on beans themselves. Beans can contain compound values as well.

Compound values, as the name implies, contain multiple pieces of data. If this sounds familiar, it should; beans themselves hold multiple pieces of data. Indeed, beans can contain other beans, which can contain yet other beans, and so on, indefinitely.

As an example of how this might be useful, consider how a bean would be used to model a home entertainment system, which may contain many individual components, such as an amplifier, CD player, cassette player, and radio tuner. The system as a whole may have certain properties, such as which component is currently playing and the overall color and size of the system. In addition, each individual component has its own set of properties. The CD player has a property representing the name of the disc it currently contains, the tuner has a property indicating the station it is currently tuned to, and so on.

It would in principle be possible to give all the properties of the components to the system as a whole, but this is bad design. It is much better to encapsulate logical units as separate beans. This design allows more complex beans to be constructed incrementally by using the individual building blocks, in the same way that using the jsp:include tag allows complex pages to be built up from smaller ones.

Given the home entertainment system bean, there is no way in which the jsp:getProperty tag could be used to determine the name of the CD in the CD player. The whole CD player bean could be obtained with

<jsp:getProperty
  id="homeEntertainment"
  property="cdPlayer"/>

However, this will display the whole CD player bean. Beans as a whole have no standard representation; this might display as something cryptic, such as com.awl.ch04.jspbook.CdBean10b053, or it might display as a list of all the properties of the bean or anything else that the bean programmer has chosen. In any case, it is unlikely to display only the name of the current disc. What is needed is a way to traverse a set of compound data. Fortunately, the expression language provides a mechanism to do this.

As discussed previously, within the expression language, a single dot between two names indicates that the name on the left should be a bean and the name on the right a property. This extends in a natural way; if a property is itself a bean, it is legal to add another dot followed by the name of a property within that bean, and so on. Getting the name of CD from a CD player within a home entertainment system would therefore look something like

${homeEntertainment.cdPlayer.currentDisk}

The meaning of the multiple dots in Listing 4.7 should make more sense now. An object called pageContext holds information about the page currently being generated. Within this object is another object, called request, which holds information pertaining to the request being processed. Finally, the request object has such data as the name of the local computer, the remote computer, and so on.

4.6.1 Repeating a Section of a Page

Another important kind of compound data is a collection of an arbitrary number of values. A CD has a number of tracks, but as this number is different for different CDs, a CD bean cannot simply have a different property for each track. Similarly, a shopping cart bean will contain a number of items, but this number will change as the bean is used.

Java has many ways to manage collections of varying size, but the simplest is called an array. Arrays are lists of objects of the same type, such as arrays of strings, arrays of numbers, and arrays of CDs. Within these arrays, items are referenced by a number called the index, starting with 0.

The expression language makes it possible to pull a particular element out of such an array by placing its index within brackets. Obtaining the first track of a CD could be done with an expression like this:

${cd.tracks[0]}

Again, note how this logically follows from the way properties work: ${cd.tracks} would return the entire array; following this with [0] pulls out a particular element from that array.

Errors to Watch For

If a request is made for an index beyond the number of elements in the array, the result will be empty.

It is unusual to need to access a particular element in an array; it is more common to need to repeat some action for every element, regardless of how many there are. This process is known as iteration, and it should come as no surprise that a tag in the standard library handles it: jsp:forEach. Recall that Listing 3.13 obtained information about a CD from a serialized bean. At that point, however, there was no way to list the tracks, because the page could not know in advance how many there would be. Listing 4.8 uses the c:forEach tag to solve this problem, and the resulting page is shown in Figure 4.2.

04fig02.gifFigure 4.2. Iteration used to display every element in an array.

Listing 4.8 The forEach tag

<%@ taglib prefix="c"
    uri="http://java.sun.com/jstl/core" %>
<jsp:useBean
 id="album"
 beanName="tinderbox4"
 type="com.awl.jspbook.ch04.AlbumInfo"/>

<h1><c:out value="${album.name}"/></h1>

Artist: <jsp:getProperty name="album"
            property="artist"/><p>
Year: <c:out value="${album.year}"/></p>

Here are the tracks:
<ul>
<c:forEach items="${album.tracks}" var="track">
  <li><c:out value="${track}"/>
</c:forEach>
</ul>

The c:forEach tag takes a number of parameters. The first is the items to iterate over, which is specified by a script. The second is a name to use as a variable; within the body of c:forEach, this variable will be set to each element in the array in turn. This variable can be accessed by the expression language as a bean, which means, among other things, that the c:out tag can be used to display it.

Errors to Watch For

If something other than an array is used as the items parameter, the c:forEach tag will treat it as if it were an array with one element.

4.6.2 Optionally Including Sections of a Page

Iteration allows a page to do one thing many times. The other major type of control a page may need is determining whether to do something at all. The custom awl:maybeShow tag introduced at the beginning of this chapter handled a limited version of that problem, but the standard tag library provides a number of much more general mechanisms, called collectively the conditional tags. The most basic of these tags is called c:if.

In its most common form, the c:if tag takes a single parameter, test, whose value will be a script. This script should perform a logical check, such as comparing two values, and facilities are provided to determine whether two values are equal, the first is less than the second, the first is greater than the second, and a number of other possibilities. Listing 4.9 shows how the c:if tag can work with a bean to determine whether to show a block of text.

Listing 4.9 The if tag

<%@ taglib prefix="c"
    uri="http://java.sun.com/jstl/core" %>
<%@ taglib prefix="awl"
    uri="http://jspbook.awl.com/samples" %>
<jsp:useBean
  id="form"
  class="com.awl.jspbook.ch04.FormBean"/>
<jsp:setProperty name="form" property="*"/>

<c:if test="${form.shouldShow == 'yes'}">
 The time is:
 <awl:date format="hh:mm:ss MM/dd/yy"/>
</c:if>

Note the expression in the script for the test parameter. Two equal signs, ==, are used to check two values for equality. Here, the first value comes from a property and is obtained with the normal dotted notation. The second value, yes, is a constant, or literal, which is reflected by the single quotes around it in the script. If these quotes were not present, the expression language would look for a bean called "yes"; as no such bean exists, the result would be an error.

Listing 4.9 is similar to Listing 4.3; the major difference is that Listing 4.9 uses the standard tag instead of the custom awl:maybeShow. The downside is that the c:if tag cannot reverse a block of text; all it can do is decide whether to include its body content in the final page.

This may seem like a shortcoming but in fact reflects a good design pattern. Note that awl:maybeShow does two completely unrelated things: checks whether a value is yes, no, or reverse and reverses a block of text. Rather than making one tag do two things, it is better to have two different tags. According to the so-called UNIX philosophy of software, each piece of code should do only one thing and do it well, and there should be easy ways to knit these small pieces together. For tags, this means that each tag can be used independently or combined with other tags. In this case, if an awl:reverse tag did nothing but reverse its body content, it could be combined with the c:if tag to do the same thing as Listing 4.3. This is shown in Listing 4.10.

Listing 4.10 Splitting tags

<%@ taglib prefix="c"
    uri="http://java.sun.com/jstl/core" %>
<%@ taglib prefix="awl"
    uri="http://jspbook.awl.com/samples" %>
<jsp:useBean
   id="form"
   class="com.awl.jspbook.ch04.FormBean"/>
<jsp:setProperty name="form" property="*"/>

<c:if test="${form.shouldShow == 'yes'}">
 The time is:
 <awl:date format="hh:mm:ss MM/dd/yy"/>
</c:if>

<c:if test="${form.shouldShow == 'reverse'}">
 <awl:reverse>
   The time is:
   <awl:date format="hh:mm:ss MM/dd/yy"/>
 </awl:reverse>
</c:if>

Note that two c:if tags are used here: one to check whether the value is yes and another to check whether it is reverse. The body content of both of these tags is the same, which is rather wasteful. It means that if the body ever needs to change, it will need to be modified in two places in order to keep everything consistent. It would be better in this case to put the body in a separate file and then have both of the if tags include that file with a jsp:include tag. Now that the functionality of awl:maybeShow has been divided into two pieces, the c:if tag can be used for many other things, and the awl:reverse tag can be used to reverse unconditionally a block of text, should such a thing ever be useful.

Listing 4.10 imports two tag libraries: the standard one, which is installed as c and provides the c:if tag, and the custom one installed as awl, which provides the awl:reverse tag. This is perfectly valid; often a page will need many different tags from different libraries, and it will then need to import all of them. The only catch is that each tag library must be given a different prefix.

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