Java Reference
In-Depth Information
Catalog Requirements
N
OTE
You will need to create a Web application named
catalog
, following the steps in
Appendix A, “Web Applications and Configuring the Servlet Engine.” Make sure you
have the classes
ConnectionPool
,
Controller
, and
Service
in your Web application's
classpath.
In this chapter you will put your newly found knowledge to practical use by creating a movie
catalog system. This system will be based on the server-side implementation of the MVC as
defined in Chapter 13 “A Servlet Controller.” The basic requirements are defined as follows:
•
Movie Presentation
—The catalog interface must give the user the ability to browse a
list of movies by category.
•
Movie Selection
—When the user has found the movie they are looking for they should
be able to select the movie and have it added to the shopping cart. They can repeat these
two steps as many times as they would like until their order is complete.
•
Order Processing Requirements
—The order processing section of the catalog applica-
tion comes into action when the user has selected all of the movies they want to order. At
this point they require a method to submit the order for processing. After the order has
been submitted, it will then be transferred to the fulfillment department.
N
OTE
For this example, the submitted order will not actually be submitted to fulfillment. It
will only be acknowledged with a thank you message.
Models
This section of the requirements defines the database representation of the movie catalog
application. Only one object in the application will be modeled in the database—the Titles
table. For our purposes you will not build an object representation of the database. We will
simply use SQL and iterate over
ResultSets
.
The
Title
object that will be represented in the database is the
Movie
object itself. Each of the
Movie
object's attributes must be included in the table representation. Table 20.1 lists the
required elements needed to store a
Movie
object.
