How tejask28/336project works
Project Type and Purpose
• This is a Java EE dynamic web application (a monolithic full-stack web app) built with JSP, Servlets, and JDBC.
• It runs on Tomcat (Dynamic Web Module 6.1), uses Java 17, and connects to a MySQL database to support flight search, user/admin/customer-rep management, and portal pages.
Top-Level Components
a. Client Tier (Browser)
• JSP pages (src/main/webapp/*.jsp)
• Static assets (CSS under /css, JS under /js)
b. Web Server / Application Container
• Tomcat V11 hosting:
– Presentation Layer: JSP
– Controller Layer: Servlet classes (Login, Logout, SearchFlightsServlet, Admin, CustRep)
– Model / DAO Layer: Java beans (User, Admin, CustRep) and MySQL.java (JDBC connection & queries)
c. Database Tier
• MySQL Server accessed via mysql-connector-j JDBC driver
Relationships & Interactions
• Browser requests a JSP (e.g., SearchFlights.jsp).
• JSP sends form/action requests to a Servlet (annotated URL patterns).
• Servlet uses MySQL.java to open a JDBC connection and execute SQL on MySQL.
• Servlet processes ResultSet, populates Java beans (User, Flight data if implemented), stores data in request/session.
• Servlet forwards back to a JSP (e.g., results.jsp) which renders the view.
Architectural Patterns & Design Principles
• MVC pattern:
• Model: Java beans + JDBC layer
• View: JSP + static CSS/JS
• Controller: Servlets
• Monolithic deployment inside a single WAR on Tomcat.
• Layered separation (Presentation, Business, Data Access).
Technologies & Frameworks
• Java 17, Jakarta Servlet API 5.0
• JSP 3.x
• JDBC (mysql-connector-j 9.x)
• Apache Tomcat 11
• MySQL relational database
Final Touches
• Be exhaustive: include all servlets and JSPs that form entry points.
• Layers distinctly—don’t lump JSP and Servlets together.