Scribd
Upload
106 views

Assignment 4

This document provides instructions for Assignment #4 in the CPRG 352 - Web Application Programming course. Students are asked to build a web application called ValidateWithEJB that uses Stateless Session Beans to validate user login attempts and manage password resets and account deletions. The application must be implemented as a Java EE project with JSPs and servlets in the war sub-project and SLSBs in the ejb sub-project. It connects to a MySQL database and allows users to be listed, have their password reset, and be deleted from the database. Screenshots provide a sample run of the application.

Uploaded by

arminaz321
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
106 views

Assignment 4

This document provides instructions for Assignment #4 in the CPRG 352 - Web Application Programming course. Students are asked to build a web application called ValidateWithEJB that uses Stateless Session Beans to validate user login attempts and manage password resets and account deletions. The application must be implemented as a Java EE project with JSPs and servlets in the war sub-project and SLSBs in the ejb sub-project. It connects to a MySQL database and allows users to be listed, have their password reset, and be deleted from the database. Screenshots provide a sample run of the application.

Uploaded by

arminaz321
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

CPRG 352 Web Application Programming

SAIT, Fall 2014


ASSIGNMENT #4 User Management with Stateless Session Beans (SLSB)

Due: Wednesday, 19th November 2014, by 5pm. (Note that D2L will not allow late submissions!)
Submission: Create a .zip archive of the entire project directory and upload it to D2L. Please DO NOT
email the submission to the instructor!

Problem
For this assignment you are required to build a web application called ValidateWithEJB. This application
uses Stateless Enterprise Session Beans (SLSB) to validate a users login attempts (against our users
MySQL database), and to manage the users password reset or account deletion.
The main focus of this assignment is the correct use of the SLJBs to perform back-end work on behalf of
the application. There is no requirement to secure the main page of the application (admin.jsp), so its
alright if users can navigate directly to that page without logging in.
The application must be implemented as a NetBeans Java EE/Enterprise Application project called
ValidateWithEJB. The JSPs and servlets must go in the -war sub-project, and the SLSBs must be
implemented in the -ejb sub-project.

Sample Run of Application

Screenshot 1: Application is run

Page 1 of 5

Screenshot 2: user clicks on Login button without providing data

Screenshot 3: user provides invalid user data and clicks on Login button

Screenshot 4: user provides valid user data and clicks on Login button

The list of users is dependent upon the contents of the users table in the database.

Page 2 of 5

The Logout hyperlink is a simple link back to the login page. There is no requirement to destroy
sessions, etc.

Screenshot 5: User clicks on the Reset link beside adam in the list

Notice the message Password reset has appeared above the table of users. In the database adams
password has been reset to the word password.

Screenshot 6: User clicks on the Delete link beside adam in the list

The message User deleted appears above the table. The row for adam has been deleted from the
users table in the database, so he disappears from the user list.

Page 3 of 5

Screenshot 7: User clicks on the Logout link

The user is taken straight back to the login page.


Application Architecture
Your solution for this assignment must use the following JEE components appropriately:

JSPs for presentation (with appropriate helper class1 to generate HTML table)

Servlets to control the application

Stateless Session Beans (SLSB) to perform application database operations on behalf of the
servlets. Only the SLSBs may update data in the database!

The application must connect to the database via a connection pool with a JNDI name of
jdbc/assign4Pool. You are being given a .sql file containing the database to use (including stored
procedures). You must use this database as-is, you can only change the data in the table, not the table
structure or the stored procedures.

The helper class can connect to the database and run a stored procedure (getAllUsers) to return the user data (it
may not update the database!)

Page 4 of 5

The following diagram shows how you could structure your solution:

Page 5 of 5

You might also like