COMP 3631 Java Web Applications

1
COMP 3631Java Web Applications

• Assignment 1

2
Objective

• To develop a web application that allows users to
  access a remote database
• Consider this the first stage in the development
  of a larger term project
• In stage 1 we will concentrate on the controller
  and business layers (Servlets and beans/utility
  classes)
• Later stages will more fully develop the
  presentation layer (JSP)

3
Database Requirements

• You will be using the remote databases that has
  been set up for your use you already have the
  appropriate information to connect to this
  database see your Day04 notes for drivers and
  connection information.
• You will create an address table to store the
  following personal contact information.
• A00123456_Members
• MemberID(int), firstName(varchar),
  lastName(varchar), Address(varchar),
  City(varchar), Country(varchar), Code(char),
  PhoneNumber(char), EMail(varchar)
• You may add other fields as you require

4
Application Requirements

• For now, Your application will be able to
• SELECT, INSERT
• Other operations will be implemented in A-2 once
  we have explored JSP
• INSERTS will be done via an HTML form.
• Output from SELECT queries should be displayed in
  HTML table format
• You will develop a presentation class that will
  wrap an HTML table around your output data.
• This class will from the basis of a Custom Tag
  later on
• SQL syntax will be completely hidden from the
  user. They will not be required to provide
  anything more than the input data and search
  criteria

5
Application Requirements

• A home page should be presented to the user,
  welcoming them to the application - this can be a
  simple HTML page.
• Cookies will be used to store retrievable data
  from the client browser. You are to come up with
  your ideas as to what data is stored.
• NOTE To save marking time please provide a
  readme file explaining how you used Cookies

6
Application Requirements

• Use of headers and status codes is expected for
  confirming MIME type on the client browser,
  Cache-Control, generating error pages, and etc.
• NOTE To save marking time please provide a
  readme file explaining how you used headers
• User input for INSERTS will be validated on both
  the browser and the server side.

7
Design Requirements

• The application will follow the Model 1.5
  architecture
• NOTE Servlet classes should not have a direct
  role in processing data, nor in generating HTML
  output. They should be used purely as controllers
  in this assignment.
• Non-Servlet classes will be used to perform the
  processing functionality of the application, as
  well as building the presentation code

8
Design Requirements

• Suggested approach
• Requests are received by the Servlet
• Data is processed by the bean classes
• Returning data will be displayed in HTML format
  generated inside HTML utility classes only
• Your Servlet functions as a controller menu
  from which all requested DB operations are
  forwarded to other classes.
• NOTE There is to be only one class that extends
  HttpServlet for the Entire application.

9
Other Considerations

• The applications must be set up to run on
  jakarta-tomcat-6.0.xx web server
• All required files and source files will be
  submitted in ltstudentgt.war format
• eg. A00123456.war
• All source code and support files are to be held
  within the application context. The only set-up
  required by the instructor will be to deploy the
  .war file

10
Evaluation

• Assignment 1 will be assessed on a mark out of
  10
• Marking considerations
• Design/Organization
• DB functions
• Presentation aspects
• Header use
• Cookie use
• Validation
• DD use
• Only the technologies covered to this point in
  the course is eligible for Assignment 1. (No JSP
  at this stage)

11
Final Notes

• Marks will be partly based on creativity and
  imagination. You want to make this an interesting
  and unique experience for the user (me).
• Be advised that this application must run out of
  the box. All that should be required from my end
  is installing your .war file.
• Be sure to include the home URL information in
  the readme file (preferably at the top).
• If I have difficulty running your submission,
• I WILL NOT TAKE THE TIME TO FIX IT!

12
Submission

• Due Date
• WEEK 6 May 26, 2009
• Files will be submitted in .war format to
  ftp//share.bcit.ca/In/COMP/3631/Assignment 1/
• Late submissions will not be accepted! Project
  must be handed in no later than the due date
  above.