How tejask28/cs336-flight-reservation-full-stack-web-app works
Project type and purpose
• This is a Java-based dynamic web application (three-tier architecture) built on Tomcat (Java Servlet container) with JSP for the view layer, Java Servlets and helper classes for the controller/business layer, and MySQL as the persistence layer.
• Purpose: airline flight search and reservation system with user Q&A, wait-list management, reporting, and administrative/customer-rep management.
File structure
• Top level:
• src/main/java – all Java classes and servlets
• src/main/webapp – JSP pages, static assets (css/js), web.xml, lib (connectors)
• build – compiled classes
• .settings, README, project config for Eclipse/Tomcat
• Patterns:
• MVC-style: JSP (View) → Servlets (Controller) → MySQL.java + model classes (Domain + DAO) → MySQL DB (Model)
• Feature modules grouped by servlet names: search, reservation, reporting, user/Q&A, admin, customer-rep.
README for additional insights
• Stack: Java 17, Tomcat 11, Dynamic Web Module 6.1, MySQL connector, Jakarta Servlet API
• Runtime flow: JSPs submit requests to Servlets via annotations; Servlets use MySQL.java to open JDBC connections, run SQL, populate responses, forward/redirect back to JSPs.
Detail without over-splitting
• Logical group of servlets as a module rather than every single servlet class
• DAO/Model layer collectively, then highlight MySQL.java and key domain objects
• Flow of data and control is clearly visible from client to DB and back