priya-priyadharshini/airline-reservation-system-fixed

Purpose and Runtime

This is a server-rendered airline reservation system: users register, search flights, select seats, add passengers, pay, and view tickets/bookings; administrators manage flights, users, and bookings. It is a Java Maven application with Spring-style application, controller, service, repository, and template layers. Entry point: airline-reservation-system/src/main/java/com/airline/AirlineReservationSystemApplication.java; build/runtime definition: airline-reservation-system/pom.xml.

HTTP UI and Entry Boundaries

MVC controllers accept browser requests, place model data for server rendering, and divide routes by role and workflow:

• Authentication: src/main/java/com/airline/controller/AuthController.java

• User booking workflow: src/main/java/com/airline/controller/UserController.java

• Administrative operations: src/main/java/com/airline/controller/AdminController.java

Views are Thymeleaf-style templates under src/main/resources/templates/, notably user search/seat/payment pages and admin dashboards. Static styling is served from src/main/resources/static/css/style.css.

Authentication and Authorization

AuthController handles login and registration through request DTOs. AuthInterceptor is the central request boundary for authenticated/authorized access, while AppConfig likely registers interceptor and MVC behavior:

• src/main/java/com/airline/config/AuthInterceptor.java

• src/main/java/com/airline/config/AppConfig.java

• src/main/java/com/airline/entity/User.java

• src/main/java/com/airline/entity/Role.java

The application distinguishes normal users from administrators and routes them into separate controller/template areas.

Flight Inventory and Search

Flight availability is modeled through flights and seats, including status fields. User search presents candidate flights, while administrators create/update flight inventory:

• src/main/java/com/airline/service/FlightService.java

• src/main/java/com/airline/entity/Flight.java

• src/main/java/com/airline/entity/Seat.java

• src/main/java/com/airline/repository/FlightRepository.java

The key control boundary is service-layer enforcement between controllers and persistence; repositories encapsulate database access.

Booking Lifecycle

BookingService is the primary transactional domain coordinator. The expected lifecycle is flight selection → seat selection → passenger capture → booking/payment → ticket display/history. Its persisted aggregate spans booking, passenger, payment, ticket, and seat state:

• src/main/java/com/airline/service/BookingService.java

• src/main/java/com/airline/entity/Booking.java

• src/main/java/com/airline/entity/Passenger.java

• src/main/java/com/airline/entity/Ticket.java

Status enums (BookingStatus, PaymentStatus, FlightStatus) define lifecycle state boundaries.

Persistence and Initialization

The data layer uses entity-specific repositories, backed by a local H2-style database artifact at data/airline_db.mv.db. Database structure is also represented in schema.sql; startup/sample-data initialization is centralized in DataLoader:

• src/main/java/com/airline/config/DataLoader.java

• airline-reservation-system/schema.sql

• airline-reservation-system/data/airline_db.mv.db

• src/main/resources/application.properties

There are no visible integrations with payment gateways, airline APIs, message brokers, or external identity providers; payment is modeled internally.

DTO and Presentation Flow

Request-specific DTOs isolate browser form payloads from JPA/domain entities, especially for login, registration, passenger creation, and payment:

• src/main/java/com/airline/dto/LoginDto.java

• src/main/java/com/airline/dto/PassengerDto.java

• src/main/java/com/airline/dto/PaymentDto.java

Templates map directly to major workflow states: templates/user/search.html, templates/user/seats.html, templates/user/payment.html, and templates/user/ticket.html. Booking/ticket codes are likely generated through src/main/java/com/airline/util/CodeGenerator.java.