Home > Articles > Web Services > XML

This chapter is from the book

Data Source for Reports

The data source for the examples in this and the following chapters come from two tables in the xmlbook database created in Appendix A,"Setting Up." The data in these tables contains some very basic information about clinic patients and their health ailments. These tables are ReportClientData and ReportClientAilment and between them there is a one-to-many relationships. That is, for each patient in ReportClientData, there might be multiple ailment records in ReportClientAilment. This relationship was created, and will be used in the next two chapters, to aid in demonstrating stylesheet methods for dealing with these types of data relationships.

Creating Database Data

The first thing that must be done is to populate the two previously mentioned tables with data. A JSP has been created to create as many records as are necessary for this purpose, and its description follows. This JSP contains a simple form that allows the user to enter the number of client records to be created.

When the form is submitted, the same JSP will begin by creating the requested number of client records. As each client record is created, a random number of ailment records are created corresponding to that client record.

The JSP named CreateDBData.jsp found in Listing 11.1 begins with an import statement and the small HTML form that allows the user to enter the number of rows of data that are created. Next, the variables are set, and the parameter entered through the form is parsed through a try-catch block as follows:

try{
    client_rows = Integer.parseInt(request.getParameter("client_rows"));
}
//catch any and all errors with form data
catch(NumberFormatException e){
    client_rows = 0;
}

If any errors result from the parsing of the form variable, such as a nonexistent value or a non-integer value, the parameter is set to 0 in the preceding catch block. This will prevent the creation of any new records.

After creating our database Connection and Statement objects, the looping construct that will insert client records into the database begins:

for(int i = 0; i < client_rows; i++){
    db_statement.execute(createQueryClient());
    ResultSet rs = db_statement.executeQuery("select LAST_INSERT_ID()");
    rs.last();
    int last_insert_id = rs.getInt(1);

Each iteration of the preceding for loop will insert one record into the ReportClientData table. After which, a statement is executed, and the resulting ResultSet is traversed to find the identity value of the newly inserted record.

This identity value is used to key ailment records with a client record. The identity value of the corresponding client record will be contained in each ailment record. This will result a one-client-to-many-ailments relationship that will be used in the following reporting chapter.

Next, a random number is generated to determine how many ailment records will be created for the current client. This number is used to loop through the creation of each ailment record:

int client_ailment = (int) (Math.random() * 5);
for(int k = 0; k < client_ailment; k++){
    try{
       db_statement.execute(createQueryAilment(last_insert_id));
       out.print("<br />Ailment added for record index: " +
           last_insert_id + ". With " + (k+1) + " out of " +
           client_ailment + " Records.");
       ailment_rows++;
    } catch (SQLException e){
         out.print("<br />Ailment skipped for record index:" +
             last_insert_id + ". Due to duplicate." );
    }
}

The processing of these statements is wrapped in a try-catch block to enable the handling of SQLExceptions. All the data is created randomly, and this causes the occasional duplicate ailment record to be created. Duplicates are unacceptable in this table because each client can only have one record indicating an ailment. This duplication error is handled in the preceding catch block, and permits the rest of the processing to continue.

Next is the code that outputs status statements and catch blocks to catch the various exceptions that the previous statements can create. The page declaration follows the end of the scriptlet.

This is where the methods that create our dates, names, and other record data reside. Following these are the methods that bring it all together to create the complete insert statements executed against the database.

The complete JSP that will dynamically create and insert data can be found in Listing 11.1 and should be saved as \webapps\xmlbook\chapter11\CreateDBData.jsp.

Listing 11.1 CreateDBData.jsp in Its Complete Form

<%@page import = "java.sql.*" %>

<html>
<head><title></title></head>
<body>
<form method="post">
<table>
    <tr>
        <td align="right">Number of rows to create:</td>
        <td><input type="text" name="client_rows" value="" size="5"/></td>
    </tr>
<tr>
    <td colspan="2" align="left">
        <br /><br /><input type="submit" value="Create Records" />
    </td>
</tr>
<table>

</form>

<%
    // 1. Initialize variables
    int client_rows;
    String final_status   = "There were 0 Client Data records added.";
    String db_query    = "";
    String db_location    = "jdbc:mysql://localhost/xmlbook";
    String db_driver = "org.gjt.mm.mysql.Driver";
    int ailment_rows = 0;

    try{
        client_rows = Integer.parseInt(request.getParameter("client_rows"));
    }
    //catch any and all errors with form data
    catch(NumberFormatException e){
        client_rows = 0;
    }

    // 2. Make a database connection
    Connection db_connection = null;
    try{
        Class.forName(db_driver);
        db_connection = DriverManager.getConnection(db_location);
        Statement db_statement = db_connection.createStatement();

     // 3. Create records for ReportClientData table in xmlbook database
        for(int i = 0; i < client_rows; i++){
            db_statement.execute(createQueryClient());
            ResultSet rs = db_statement.executeQuery
                ("select LAST_INSERT_ID()");
            rs.last();
            int last_insert_id = rs.getInt(1);
            int client_ailment = (int) (Math.random() * 5);
            for(int k = 0; k < client_ailment; k++){
                try{
                    db_statement.execute(createQueryAilment(last_insert_id));
                    out.print("<br />Ailment added for record index: " +
                        last_insert_id + ". With " + (k+1) + " out of " +
                        client_ailment + " Records.");
                    ailment_rows++;
                } catch (SQLException e){
                    out.print("<br />Ailment skipped for record index:" +
                        last_insert_id + ". Due to duplicate." );
                }
            }
            if (client_rows -1 == i)
                final_status = "There were " + client_rows +
                        " Client Data records added.";
        }

    }
    catch (ClassNotFoundException e)
    {   final_status  = " Error creating database drive class!";
        final_status += " <br />" +  e.toString();
    }
    catch (SQLException e)
    {   final_status  = " Error processing the SQL!";
        final_status += " <br />" +  e.toString();
    }
    finally
    {
        /* We must close the database connection now */
        try
        {   if (db_connection != null)
            { db_connection.close(); }
        }
        catch (SQLException e)
        {   final_status  = "Error in closing connection.";
            final_status += " <br />" +  e.toString();
        }
    }
%>

<br /><br />
<font color="blue"><%=final_status%>
    <br />And <%=ailment_rows%> Ailment Data records added.
</font>
<br /><br />
</body>
</html>

<%!
char letters[] = {'a', 'b', 'c', 'd', 'e', 'f',
    'g', 'h', 'i', 'j', 'k', 'l', 'm', 'n', 'o',
    'p', 'q', 'r', 's', 't', 'u', 'v', 'w', 'x', 'y', 'z'};

private String createString(int length){

    String result = "";

    for(int i = 0; i < length; i++){
        int temp = (int) (Math.random() * 26);
        //capitalize the first letter in this string
        if (i == 0)
            result += Character.toUpperCase(letters[temp]);
        else
            result += letters[temp];
    }

    return new String(result);
}
//1 means birthdate (1930 - 1996)
//2 means ailment 10 years (1980 - 1997)
private String createDate(int year_range){

    String result = "19";

    if (year_range == 1)
        result += "" + (30 + (int) (Math.random() * 67));
    else
        result += "" + (80 + (int) (Math.random() * 18));
    result += "-" + (1 + (int) (Math.random() * 12));
    result += "-" + (1 + (int) (Math.random() * 28));

    return new String(result);
}

private String createColor(){

    String result = "";
    int pick_a_color = (int) (Math.random() * 6);

    switch (pick_a_color) {
        case 0: result = "red";
                break;
        case 1: result = "yellow";
                break;
        case 2: result = "blue";
                break;
        case 3: result = "green";
                break;
        case 4: result = "purple";
                break;
        case 5: result = "orange";
                break;
        default: result = "black";
    }
    return result;
}

private String createQueryClient(){
    String db_query  = " insert into ReportClientData ";
    db_query += "(RCD_lname,RCD_fname,RCD_clinic,RCD_dob,RCD_color)";
    db_query += " values (";
    db_query += "'" + createString( 7 ) + "' ,";
    db_query += "'" + createString( 5 ) + "' ,";
    db_query += "'" + (1 + (int) (Math.random() * 5)) + "' ,";
    db_query += "'" + createDate(1) + "' ,";
    db_query += "'" + createColor() + "')";

    return db_query;
}
private String createQueryAilment(int clientID){

    String db_query  = " insert into ReportClientAilments ";
    db_query += "(RCA_medicalailment,RCA_datefound,RCA_clientID)";
    db_query += " values (";
    db_query += "'" + createString( 1 ) + "' ,";
    db_query += "'" + createDate(2) + "' ,";
    db_query += "'" + clientID + "' )";

    return db_query;
}
%>

Now that some data exists, let's start creating some reports. The first step in this process is creating a class that will create a JDOM representation out of a ResultSet.

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