How harismuneer/flight-booking-system-javaservlets_app works
Main Components
• Frontend / Presentation Layer: This includes JSP pages, HTML/CSS/JavaScript assets, and the UI templates found under the “build/web”, “web”, and “assets” directories. These are what the end-users (Admins, Managers, Customers) interact with.
• Application / Business Layer:
• Java Servlets and Managers (see files such as CustomerManager.java, LoginManager.java, LogoutManager.java, etc. located in the src/java directory).
• The controllers (servlets), model classes, and filters (e.g., SecurityFilter.java, XSSFilter.java) that implement the core logic and validations.
• Data Layer: The Microsoft Access Database (notably, files such as airlines.accdb present in the project) and any persistence logic interacting with it.
• Security Components: Highlight the use of Tomcat Roles for authentication/authorization and the implemented security filters to prevent SQL Injection and XSS. Indicate distinct user roles (Airline Admin, Airline Manager, Customer).
Relationships and Data Flow
• How the Servlets interact with the Model components (for instance, invoking methods on Customer, Flight, and Seat models).
• Connection between the Business Layer and the Data Layer, indicating database read/write operations (Microsoft Access).
• Security checkpoints (e.g., filters executing before servlets) to intercept input data.
Architectural Patterns and Design Principles
• MVC Pattern: Clearly separate the view (JSPs), controller (Java Servlets, Managers), and model (Java classes representing business entities).
• Layered Architecture: Present the system as distinct layers (presentation, business, data, and integration service layer).
Relevant Technologies and Libraries
• Frontend technologies: HTML, CSS, JavaScript, jQuery, Bootstrap, and JSPs.
• Server-side: Java Servlets, Java Models, and filters.
• Database: Microsoft Access.
• Web Services: SOAP implemented using JAX-WS (with provided libraries like webservices-api.jar and related JARs).
• Security: Tomcat security via role-based access, along with internal security filters to mitigate SQL Injection and XSS risks.
• Build Tools: Use of Ant scripts (build.xml) and NetBeans project configurations.
Elements
• Labels for each component (e.g., "Presentation Layer (JSPs and Assets)", "Controllers/Managers (Servlets, Java logic)", "Model (Entities and Business Objects)", "Database (MS Access)", "Security (Filters, Tomcat Roles)", "SOAP Web Services (PriceAndSeats)".
• HTTP request flow from users through JSP pages to Servlets.
• Data operations between Servlets and the Database.
• Service calls to the external SOAP Web Services.
• Configuration or intermediary elements such as the use of filters for security that run before the request reaches business components.
• That the representation of external services (WSTester and SOAP Web Services) is visually distinct to emphasize that they are separate from the main application logic.