Home > Articles

📄 Contents

  1. Understanding BeanUtils
  2. Using BeanUtils to Generate Forms
  3. Summary
This chapter is from the book

Using BeanUtils to Generate Forms

Given the information already present in a JavaBean, the sample application will use BeanUtils to create a new library based on a new class, FormBean. FormBean generates an HTML form directly from the JavaBean information as rendered by BeanUtils. Each property results in a single label and a single text field. The label is generated automatically from the property name (for example, getFirstName is automatically labeled First Name). When the form is submitted, FormBean will attempt to set the JavaBean properties using the submitted values.

Although FormBean is not a complete framework (for example, array-based properties are not supported), it does illustrate the power of JavaBeans in conjunction with BeanUtils.

Sample JavaBeans

This example is based on the simple JavaBean shown in Listing 7-1. Note the three properties: two of type String, one of type int.

In order to demonstrate the lifecycle as handled by FormBean, the application needs to have some mechanism for storing a value. Listing 7-2 shows how the application tracks the user.

Listing 7-2 Tracking the User

package com.cascadetg.ch07;

public class UserManager
{
    static private User user = new User();

    static public User getUser() { return user; }

    static public void setUser(User in) { user = in; }
}

Presenting the Form

Given the User JavaBean, FormBean generates a form, as shown in Figure 7-2.

If a user enters incorrect data for the required property type, FormBean automatically generates and reports the error, as shown in Figure 7-3.

Figure 7.2Figure 7-2 Initial FormBean form.

Figure 7.3Figure 7-3 Handling a FormBean form error.

After the user corrects any errors and resubmits the form, FormBean is used to accept the submission, as shown in Figure 7-4.

Figure 7.4Figure 7-4 Corrected FormBean form.

The entire JSP file to generate and handle this form is shown in Listing 7-3. Note the .error style defined to highlight the errors.

Listing 7-3 FormBean JSP

<%@ page language="java" im-
port="com.cascadetg.ch07.*,org.apache.commons.beanutils.*" errorPage="" %>
<%
    FormBean myFormBean = new FormBean(User.class, UserManager.getUser());
    String notification = "Welcome!";
    if(request.getParameter("Submit") != null)
    {        
        if(myFormBean.updateValue(request))
            notification = "Form accepted!";
        else
            notification = "Form incorrect: fix errors";
    }    
%>
<html>
<head><title>BeanUtils Demo</title>
<style type="text/css">
<!-- 
.error { color: #FF0000; }
-->
</style>
<link href="../ch03/default.css" rel="stylesheet" type="text/css">
</head>
<body>
<table>
<form name="form1" method="post" action="">
<%= myFormBean.toHTMLForm()%>
<tr><td colspan="3"><input type="submit" name="Submit" value="Submit">
</td></tr>
</form>
</table>
<p><%= notification %></p>
</body>
</html>

Even a simple form with minimal update and validation logic would be painful to implement by hand with JSP. For a web application with dozens of such forms, a lot of tedious work could be eliminated through the use of a framework like FormBean.

FormBean

The initialization of the FormBean is shown in Listing 7-4. As you can see, the FormBean uses the class and optionally an instance to configure the form. If no instance is passed in, FormBean will attempt to instantiate one. Either way, the FormBean keeps track of both the original class and instance, and then it wraps the class in a DynaClass and the instance in a DynaBean (using WrapDynaClass).

Listing 7-4 FormBean Initialization

package com.cascadetg.ch07;

import java.util.HashMap;
import java.util.Map;

import javax.servlet.http.HttpServletRequest;

import org.apache.commons.beanutils.BeanUtils;

import org.apache.commons.beanutils.DynaBean;
import org.apache.commons.beanutils.DynaClass;
import org.apache.commons.beanutils.DynaProperty;
import org.apache.commons.beanutils.WrapDynaBean;
import org.apache.commons.beanutils.WrapDynaClass;

public class FormBean
{
    private HashMap errors = new HashMap();

    // The class refers to the compiled version of the class
    private Class baseClass;
    private DynaClass dynaClass;

    // The object refers to the runtime (in-memory) version
    private Object baseObject;
    private DynaBean dynaObject;

    private DynaProperty[] properties;

    // Used to help format the resulting text boxes
    private int displayStringLength = 40;
    private int maxStringLength = 100;

    /** For creation forms */
    public FormBean(Class myClass)
    {
        baseClass = myClass;
        dynaClass = WrapDynaClass.createDynaClass(baseClass);
        properties = dynaClass.getDynaProperties();
        try
        {
            baseObject = myClass.newInstance();
            dynaObject = new WrapDynaBean(baseObject);
        } catch (Exception e)
        {
            System.err
                    .println("FATAL ERROR: Unable to instantiate "
                            + dynaClass.getName());
            e.printStackTrace();
        }
    }

    /** For update forms */
    public FormBean(Class myClass, Object myObject)
    {
        baseObject = myObject;
        dynaObject = new WrapDynaBean(baseObject);
        baseClass = myClass;
        dynaClass = WrapDynaClass.createDynaClass(baseClass);
        properties = dynaClass.getDynaProperties();
    }

Given the class and an instance, FormBean has the information it needs to create a form. As shown in Listing 7-5, FormBean loops through the properties to generate the label and the input form and to set the default values for the form based on the object instance. Note that errors are collected in a java.util.Map, with the key being the property and the value being the error message.

Listing 7-5 FormBean Form Generation

/** Converts the object into a simple HTML form. */
    public String toHTMLForm()
    {
        StringBuffer output = new StringBuffer();

        for (int i = 0; i < properties.length; i++)
        {
            String currentProperty = properties[i].getName();
            if (currentProperty.compareTo("class") != 0)
            {

                // Start the row
                output.append("<tr>");

                // The cell for the label
                output.append("<td>");
                output.append(FormBeanUtils
                        .formatName(currentProperty));
                output.append("</td>");

                // The cell for the input form element
                output.append("<td>");
                output.append("<input ");
                FormBeanUtils.appendAttribute(output, "name",
                        currentProperty);

                // The cell for the current value, if there is
                // one
                if (this.dynaObject.get(currentProperty) != null)
                {
                    FormBeanUtils.appendAttribute(output,
                            "value", this.dynaObject.get(
                                    currentProperty).toString());
                }

                // Finish the input cell
                FormBeanUtils.appendAttribute(output, "size",
                        displayStringLength + "");
                FormBeanUtils.appendAttribute(output,
                        "maxlength", maxStringLength + "");
                output.append(">");
                output.append("</td>");

                // This cell displays any errors for this
                // property
                output.append("<td class='error'>");
                if (errors.containsKey(currentProperty))
                {
                    output.append(errors.get(currentProperty)
                            .toString());
                }
                output.append("&nbsp;</td>");

                // Finish up this row
                output.append("</tr>");
            }
        }

        return output.toString();
    }

Listing 7-6 shows how a submitted form is handled. Note that the logic is expressed in terms of a Map (not explicitly tied in to the servlet model), allowing the FormBean to be tested outside of the context of a container. The BeanUtils class is used to attempt to set the values of the bean using the string submitted by the user. A try/catch block wraps the conversion attempt, and failures are logged to a Map for later display to the user.

Listing 7-6 FormBean Update Request

/**
     * Returns true if all of the values pass validation.
     * Otherwise, returns false (the user should therefore be
     * prompted to correct the errors).
     * 
     * The incoming Map should contain a set of values, where the
     * incoming values are a single key String and the values are
     * String[] objects.
     */
    public boolean updateValue(Map in)
    {
        // Initialize the converters - we want format exceptions.
        FormBeanUtils.initConverters();

        boolean isGoodUpdate = true;

        for (int i = 0; i < properties.length; i++)
        {
            String key = properties[i].getName();
            Object value = in.get(key);
            try
            {
                BeanUtils.setProperty(baseObject, key, value);
            } catch (Exception e)
            {
                if (value != null)
                {
                    errors.put(key, "Value of "
                            + FormBeanUtils.formatName(key)
                            + " may not be '"
                            + ((String[]) value)[0].toString()
                            + "'");
                } else
                    errors.put(key, "Value may not be null");
                isGoodUpdate = false;
            }
        }

        return isGoodUpdate;
    }

    /**
     * Returns true if all of the values pass validation.
     * Otherwise, returns false (the user should therefore be
     * prompted to correct the errors).
     */
    public boolean updateValue(HttpServletRequest request)
    {
        Map in = request.getParameterMap();
        return this.updateValue(in);
    }

Listing 7-7 demonstrates how the FormBean was developed—outside of a servlet container.

Listing 7-7 FormBean

/**
     * Note that this particular design allows you to test your
     * bean programmatically, outside of the context of a web
     * application server.
     */
    public static void main(String[] args)
    {
        FormBean myFormBean = new FormBean(User.class);
        System.out.println(myFormBean.toHTMLForm());

        User myUser = new User();
        myUser.setClearance(5);
        myUser.setFirstName("Bob");
        myUser.setLastName("Smith");

        myFormBean = new FormBean(User.class, new WrapDynaBean(myUser));
        System.out.println(myFormBean.toHTMLForm());

        Map myMap = new HashMap();
        myMap.put("firstName", new String[] { "Ralph"});
        myMap.put("lastName", new String[] { "Bingo"});
        myMap.put("clearance", new String[] { "5"});
        myFormBean.updateValue(myMap);
        System.out.println(myFormBean.toHTMLForm());

        myMap.remove("clearance");
        myMap.put("clearance", new String[] { "invalid"});
        myFormBean.updateValue(myMap);
        System.out.println(myFormBean.toHTMLForm());
    }
}

FormBeanUtils

A few utility methods are needed to support the FormBean, as shown in Listing 7-8. The formatName method is used to generate proper English labels from JavaBean properties. The appendAttribute method is used to ease the generation of HTML-style attribute values. Most importantly, the initConverters method is used to cause the BeanUtils property setter to throw an exception in the event of a failed conversion attempt. By default, BeanUtils will silently fail if a conversion attempt fails. By installing the converter as shown, failed attempts to convert a String to an int or Integer value will generate an exception. If you wish to support additional property types and generate errors for failed conversions, you can install additional converters. The BeanUtils package includes converters for all core Java types (as listed earlier in this chapter), and you can create your own customer converters as well.

Listing 7-8 FormBean Utilities

package com.cascadetg.ch07;

import org.apache.commons.beanutils.ConvertUtils;
import org.apache.commons.beanutils.Converter;
import org.apache.commons.beanutils.converters.IntegerConverter;

public class FormBeanUtils
{
    /**
     * A utility function, takes a standard JavaBean property
     * name and converts it to a nice US English spacing.
     * 
     * For example, firstName = First Name   */
    public static String formatName(String in)
    {
        String result = new String();

        for (int i = 0; i < in.length(); i++)
        {
            if (Character.isUpperCase(in.charAt(i)))
            { result = result + (" "); }
            result = result + (in.charAt(i) + "");
        }

        String result2 = new String();

        for (int i = 0; i < result.length(); i++)
        {
            if (Character.isDigit(result.charAt(i)))
            { result2 = result2 + (" "); }
            result2 = result2 + (result.charAt(i) + "");
        }

        char titleChar = result2.charAt(0);
        String result3 = Character.toUpperCase(titleChar) + "";

        result3 = result3
                + (result2.substring(1, result2.length()));

        return result3;
    }

    /**
     * A utility method, used to add an attribute in the form
     * attribute='value' with a space afterward.
     */
    public static void appendAttribute(StringBuffer in,
            String attribute, String value)
    {
        in.append(attribute);
        in.append("='");
        in.append(value);
        in.append("' ");
    }

    static private boolean convertersInitialized = false;

    static public void initConverters()
    {
        if (!convertersInitialized)
        {
            // No-args constructor gets the version that throws
            // exceptions
            Converter myConverter = new IntegerConverter();

            // Convert the primitive values
            ConvertUtils.register(myConverter, Integer.TYPE);

            // Convert the object version
            ConvertUtils.register(myConverter, Integer.class);
            convertersInitialized = true;
        }
    }
}

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