How saadahmed1122/e-learning_web_application works
Project type and purpose
• This is a full-stack e-learning web application built on Java 8, using Java Servlets (MVC pattern) for server-side logic, JSP/HTML/CSS/Bootstrap for the front end, and PostgreSQL for data persistence.
• It supports three user roles—Admin, Teacher, Student—and implements core LMS features (course management, content upload, messaging, registration).
File structure
• Top-level WA-HW1 folder holds a Maven webapp:
• src/main/java/MVC/Bean → plain old Java objects (model)
• src/main/java/MVC/Controller → servlets (controller)
• src/main/java/MVC/dao → data access objects (DAO layer)
• src/main/webapp → JSP pages, static assets (CSS, JS, images, plugins)
• src/main/database → SQL schema and seed scripts
• Standard Maven POM for builds, target/ holds compiled WAR layout.
• Uses PostgreSQL JDBC driver, Tomcat 10 deployment descriptor (web.xml).
Key architectural patterns
• 3-Tier architecture: Presentation (JSP + static assets), Business/Controller (Servlets + Beans), Data (DAO + PostgreSQL).
• MVC pattern: request flows from browser → servlet controller → model/DAO → DB, then back to JSP view.
• DAO pattern isolates SQL and connection management (DatabaseConnection utility).
a. Main components:
• Client browser (User interface: JSP/HTML/CSS/JS, Bootstrap, Materialize)
• Web/App Server (Apache Tomcat 10) hosting the WAR
• Presentation Layer (JSPs under webapp/)
• Controller Layer (Servlets under MVC/Controller/)
• Model Layer (Beans under MVC/Bean/)
• Data Access Layer (DAO classes under MVC/dao/)
• Database (PostgreSQL instance)
• External libraries (JDBC driver, Highlight.js plugin, Bootstrap assets)
b. Relationships & data flow:
1. Client → HTTP request → Tomcat
2. Tomcat routes to a Servlet (Controller)
3. Controller invokes DAOs via JDBC (using DatabaseConnection)
4. DAO returns model objects (Beans)
5. Controller attaches Beans to request/session and forwards to JSP
6. JSP renders HTML, JS, CSS back to browser
c. Highlighted patterns:
• MVC separation of concerns
• Three-layer separation (Presentation/Business/Data)
• DAO encapsulation of persistence logic
d. Technologies & frameworks:
• Java Servlets & JSP, MVC pattern
• Maven build, Tomcat deploy
• PostgreSQL via JDBC
• Bootstrap, Materialize CSS, custom JS/CSS, Highlight.js plugin