Home > Articles > Programming > Java

JDBC Today

This chapter is from the book

Java Design Patterns

The concept of design patterns is often heard discussed in connection with Java application design. Design patterns are used to help guide the development process. Design patterns do not represent complete, template-like solutions, but instead represent recommendations on how to solve certain recurring problems with Java development.

The concept of design patterns can be traced back to work that Christopher Alexander did with building construction architecture in the 1980s. Alexander noted that certain problems would consistently recur in building design and that certain proven solutions could be used to solve these problems. He referred to these proven solutions as design patterns.

A group of academics picked up on this work and wrote a seminal book on the subject titled, appropriately enough, Design Patterns: Elements of Reusable Object-Oriented Software. The authors of this text, Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides, are often referred to as the Gang of Four, and thus the text is often referred to as the GoF book. The authors of this text very succinctly applied the concept of design patterns to the process of developing good, object-oriented code. They used the Smalltalk language, but the solutions can easily be applied to any full-featured object-oriented language that supports polymorphism and a facility similar to Java interfaces.

Chapter 13 covers design patterns that apply to JDBC programming in more detail. What is important to note at this point is that design patterns have a significant impact on how JDBC will be used in an application. It should also be noted that design patterns can be applied at several different levels of the development process. Gamma, Helm, Johnson, and Vlissides refer to design patterns as taking the form of creational, structural, or behavioral patterns in relation to how the patterns will be used.

A design pattern that is often noted is the Model, View, Controller (MVC) design pattern. The MVC design pattern was originally applied to the Graphical User Interface (GUI) programming and describes the responsibilities of different portions of the application, as shown in Table 1–3.

As applied to a GUI application, the model portion of the application manages the data, the view displays the controls of the application (input fields, tables, list boxes), and the controller represents the event handlers for user-generated events: button clicks, list box choices, and others. In a GUI application being developed with an object-oriented language, these components would represent objects (and the class definitions for the object) that would be designed to provide for the behaviors, the responsibilities described in Table 1–3.

Table 1-3 MVC Design Pattern

Component

Responsibility

Model

Manages the application state, the data the application is using.

View

Renders the portion of the application visible to the user.

Controller

Responds to user gestures and interfaces with the model to control the application.


Table 1-4 EE Components by Tier

ier

MVC

Component

Client

View

Applet, HTML, Java Webstart

Presentation

Controller

servlet, JSP page

Business

Model

Enterprise JavaBean, JavaBean

Resource

n/a

SQL


But in order to apply this design pattern to a Web application, it is imperative that we identify which Web application components will implement the design. If we approach this design pattern using our multitiered architecture described earlier, we should expect that the view portion will be managed by the client tier, the controller will be managed the presentation tier, and the model will be managed by the business tier components. If we are using J2EE, our most likely candidate for each of these components is as follows (Table 1–4).

When viewed in this respect, the MVC pattern describes the responsibilities of the components being used and so would probably more accurately be described as an architectural design pattern. The MVC pattern alone does not describe how the specific components (the view component being used on the presentation tier, for example) would be designed. Other Java design patterns as shown later in this book do provide these details.

Using MVC as an architectural pattern, we do receive some high-level guidance about where JDBC code would be located. We would expect the JDBC calls to be placed in the components in the business tier. Located in that tier, the JDBC calls would retrieve data from the resource tier, and the Java code in the business tier would apply business logic and then return the data to the presentation tier, where it would be formatted for presentation to the user.

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