Reference no: EM132153491

The Project

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

Part_1: Product Maintenance
For this part, you'll create a series of pages that allow you to add, update, or delete a product that's available to the application.

Operation
(1) 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.
(2) 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.
(3) 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.
(4) 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

(1) Use a Product class like the one shown later in this document to store the product data.
(2) 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.
(3) 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.
(4) 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 product's price is a valid double value.
(5) If possible, get the Product.java, ProductIO.java, and product.txt files from your instructor or trainer. Otherwise, you can create these files yourself.

Part_2: Product Maintenance with custom tag validation
For this Part, you'll enhance the application described in Part_1 by adding a custom tag to validate user entries.
Specifications
(1) Use a custom tag to mark empty fields that are required on the Product page with an asterisk.

Part_3: Product Maintenance with a database using JDBC
For this Part, you'll enhance the application described in the previous Parts by modifying it so it uses a database instead of a text file to store the product data. You'll use JDBC to work with the data.
Specifications
(1) Use a class named ProductDB that's in the music.data package to add, update, and delete the products in the Product Maintenance application. This class should use JDBC.
(2) Use a connection pool as described in chapter 12.
(3) Use the music database (available on Moodle for download as DB.zip)

Part_4: Product Maintenance with a database using JPA
For this Part, you'll convert the application in the previous Parts so it uses JPA instead of JDBC to work with a database.
Specifications
(1) Add JPA annotations to the Product class.
(2) Use a class named ProductDB that's 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.
(3) Since the EclipseLink JPA provider automatically creates a connection pool, please delete any old code that creates a connection pool for JDBC.
(4) Use the music database (available on Moodle for download as DB.zip)

Part_5: Product Maintenance with SSL and authentication
For this Part, you'll enhance the application described in the previous Parts by modifying it so it uses a secure connection and only allows authorized users (refer to chapters 1-13, 15, and 16 of textbook B)

Specifications

(1) 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.
(2) Use a secure connection for all pages except the Index page.

Part_6: Product Maintenance within the Music Store web site
For this project, you'll 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)

Specifications

(1) Add the JSP files for the Product Maintenance application to the admin directory of the Music Store web site.
(2) Add the controller servlet for the Product Maintenance application to the music.admin package of the Music Store web site.
(3) 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.
(4) 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.
(5) 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 doesn't 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 isn't available.
(6) Don't break the other applications in the existing Music Store web site.

Attachment:- Project Part.rar