Answered step by step
Verified Expert Solution
Link Copied!

Question

1 Approved Answer

The projects The following pages present the user interface, operation, and specifications for each project. As you view these pages, remember that each project builds

The projects

The following pages present the user interface, operation, and specifications for each project. As you view these pages, remember that each project builds upon the previous projects.

Project 1: Product Maintenance

For this project, youll create a series of pages that allow you to add, update, or delete a product thats available to the application. (Prerequisites: chapters 1-9)

The Index page

The Products page

The Product page

The Confirm Delete page

Operation

When the application starts, it displays the Index page. This page contains a link that leads to the Products page that can be used to add, update, or delete products.

To add a new product, the user selects the Add Product button. This displays the Product page with all text fields empty. Then, the user can fill in the text fields and click on the Update Product button to add the product.

To edit an existing product, the user selects the Edit link for the product. This displays the Product page with all existing data for the product displayed. Then, the user can edit any entries and click on the Update Product button to update the data for the existing product.

To delete a product, the user selects the Delete link for the product. This displays the Confirm Delete page. Then, if the user confirms the deletion by selecting the Yes button, the product is deleted and the Products page is displayed to reflect the new data. If the user selects the No button, the Products page is displayed.

Specifications

Use a Product class like the one shown later in this document to store the product data.

Use a ProductIO class like the one shown later in this document to read and write the product data to a text file named products.txt in the WEB-INF directory.

Use a text file like the products.txt file shown later in this document as a starting point for the products that are available to the application.

Use server-side validation to validate all user entries. In particular, make sure the user enters a code, description, and price for each product. In addition, make sure the products price is a valid double value.

If possible, get the Product.java, ProductIO.java, and product.txt files from your instructor or trainer. Otherwise, you can create these files yourself.

The Product class

package music.business;

import java.text.NumberFormat;

import java.io.Serializable;

public class Product implements Serializable {

private Long productId;

private String code;

private String description;

private double price;

public Product() {}

public Long getId() {

return productId;

}

public void setId(Long productId) {

this.productId = productId;

}

public void setCode(String code) {

this.code = code;

}

public String getCode() {

return code;

}

public void setDescription(String description) {

this.description = description;

}

public String getDescription() {

return description;

}

public String getArtistName() {

String artistName =

description.substring(0, description.indexOf(" - "));

return artistName;

}

public String getAlbumName() {

String albumName =

description.substring(description.indexOf(" - ") + 3);

return albumName;

}

public void setPrice(double price) {

this.price = price;

}

public double getPrice() {

return price;

}

public String getPriceCurrencyFormat() {

NumberFormat currency = NumberFormat.getCurrencyInstance();

return currency.format(price);

}

public String getImageURL() {

String imageURL = "/musicStore/images/" + code + "_cover.jpg";

return imageURL;

}

public String getProductType() {

return "Audio CD";

}

}

The ProductIO class

package music.data;

import java.io.*;

import java.util.*;

import music.business.*;

public class ProductIO {

private static List products = null;

private static String filePath = null;

// Called once from the controller based on servlet context

public static void init(String filePath) {

ProductIO.filePath = filePath;

}

public static List selectProducts() {

products = new ArrayList();

File file = new File(filePath);

try {

BufferedReader in

= new BufferedReader(

new FileReader(file));

String line = in.readLine();

while (line != null) {

StringTokenizer t = new StringTokenizer(line, "|");

if (t.countTokens() >= 3) {

String code = t.nextToken();

String description = t.nextToken();

String priceAsString = t.nextToken();

double price = Double.parseDouble(priceAsString);

Product p = new Product();

p.setCode(code);

p.setDescription(description);

p.setPrice(price);

products.add(p);

}

line = in.readLine();

}

in.close();

return products;

} catch (IOException e) {

System.out.println(e);

return null;

}

}

public static Product selectProduct(String productCode) {

products = selectProducts();

for (Product p : products) {

if (productCode != null

&& productCode.equalsIgnoreCase(p.getCode())) {

return p;

}

}

return null;

}

public static boolean exists(String productCode) {

Product p = selectProduct(productCode);

if (p != null) return true;

else return false;

}

private static void saveProducts(List products) {

try {

File file = new File(filePath);

PrintWriter out

= new PrintWriter(

new FileWriter(file));

for (Product p : products) {

out.println(p.getCode() + "|"

+ p.getDescription() + "|"

+ p.getPrice());

}

out.close();

} catch (IOException e) {

System.out.println(e);

}

}

public static void insertProduct(Product product) {

products = selectProducts();

products.add(product);

saveProducts(products);

}

public static void updateProduct(Product product) {

products = selectProducts();

for (int i = 0; i < products.size(); i++) {

Product p = products.get(i);

if (product.getCode() != null

&& product.getCode().equalsIgnoreCase(p.getCode())) {

products.set(i, product);

}

}

saveProducts(products);

}

public static void deleteProduct(Product product) {

products = selectProducts();

for (int i = 0; i < products.size(); i++) {

Product p = products.get(i);

if (product != null

&& product.getCode().equalsIgnoreCase(p.getCode())) {

products.remove(i);

}

}

saveProducts(products);

}

}

A product.txt file that contains four products

8601 - 86 (the band) - True Life Songs and Pictures|14.95

pf01 - Paddlefoot - The first CD|12.95

pf02 - Paddlefoot - The second CD|14.95

jr01 - Joe Rut - Genuine Wood Grained Finish|14.95

Project 2: Product Maintenance with custom tag validation

For this project, youll enhance the application described in project 1 by adding a custom tag to validate user entries. (Prerequisites: chapters 1-10)

The Product page with custom tags for validation

Specifications

Use a custom tag to mark empty fields that are required on the Product page with an asterisk.

Project 3: Product Maintenance with a database using JDBC

For this project, youll enhance the application described in the previous projects by modifying it so it uses a database instead of a text file to store the product data. Youll use JDBC to work with the data. (Prerequisites: chapters 1-12)

The Products page

Specifications

Use a class named ProductDB thats in the music.data package to add, update, and delete the products in the Product Maintenance application. This class should use JDBC.

Use a connection pool as described in chapter 12.

Use the music database thats created when you follow the procedures described in appendix A (PC) or B (Mac).

Project 4: Product Maintenance with a database using JPA

For this project, youll convert the application in the previous project so it uses JPA instead of JDBC to work with a database. (Prerequisites: chapters 1-13)

The Products page

Specifications

Add JPA annotations to the Product class.

Use a class named ProductDB thats in the music.data package to add, update, and delete the products in the Product Maintenance application. This class should use the EclipseLink JPA provider.

Since the EclipseLink JPA provider automatically creates a connection pool, please delete any old code that creates a connection pool for JDBC.

Use the music_jpa database thats created when you follow the procedures described in appendix A (PC) or B (Mac).

Project 5: Product Maintenance with SSL and authentication

For this project, youll enhance the application described in the previous projects by modifying it so it uses a secure connection and only allows authorized users. (Prerequisites: chapters 1-13, 15, and 16)

The Index page

The Warning page for a secure connection

The Login page with a secure connection

The Products page with a secure connection

Specifications

Restrict access to all pages except the Index page. Only allow users in the programmer role and customer service role to access the rest of the pages in the Product Maintenance application. To do that, use the UserPass and UserRole tables in the murach database to define the usernames and passwords for these roles.

Use a secure connection for all pages except the Index page.

Project 6: Product Maintenance within the Music Store web site

For this project, youll enhance the application described in the previous projects by adding it to the admin section of the Music Store web site. (Prerequisites: 1-13,15, 16, 22 and 23)

The Login page

The Admin Menu page

The Products page

The Add/Update Product page

The Confirm Delete page

Specifications

Add the JSP files for the Product Maintenance application to the admin directory of the Music Store web site.

Add the controller servlet for the Product Maintenance application to the music.admin package of the Music Store web site.

Modify the admin/index.jsp file of the Music Store web site so it includes a button that starts the newly added Product Maintenance application.

Modify all necessary JSP, CSS, Java, and XML files within the Music Store web site so they work with the newly added Product Maintenance application.

In the controller for the Product Maintenance application, use the getRequestURI method to determine which action to process as shown in chapter 22. If the URL doesnt match any actions in your application, use the sendError method of the response object to send a 404 error to the user to indicate that the page isnt available.

Dont break the other applications in the existing Music Store web site.

Step by Step Solution

There are 3 Steps involved in it

Step: 1

blur-text-image

Get Instant Access to Expert-Tailored Solutions

See step-by-step solutions with expert insights and AI powered tools for academic success

Step: 2

blur-text-image

Step: 3

blur-text-image

Ace Your Homework with AI

Get the answers you need in no time with our AI-driven, step-by-step assistance

Get Started

Recommended Textbook for

Records And Database Management

Authors: Jeffrey R Stewart Ed D, Judith S Greene, Judith A Hickey

4th Edition

0070614741, 9780070614741

More Books

Students also viewed these Databases questions