a-man24x7/train-booking-system

1. Purpose and deployment

A server-rendered Java train-booking application for customers and administrators. It is deployed as a Maven WAR-style web application to Tomcat 9, with HTML pages under WebContent/ and servlet routing configured in WebContent/WEB-INF/web.xml. Browser entry is WebContent/index.html.

2. Request and presentation boundary

HTTP requests are handled by role- and use-case-specific Java servlets. Many *Fwd servlets appear to forward users to HTML views, while action servlets process form submissions and redirect/forward based on results.

• src/com/aman/servlets/UserLoginServlet.java

• src/com/aman/servlets/AdminLogin.java

• src/com/aman/servlets/ErrorHandlerServlet.java

Views are static HTML pages, including separate user/admin homes and booking/search/payment screens:

• WebContent/UserHome.html

• WebContent/AdminHome.html

• WebContent/BookTrains.html

3. Identity, roles, and session-oriented flows

Customer registration/login, profile updates, password changes, and logout are handled in the servlet layer and delegated to user services. Admin authentication and logout are separate flows. Role meaning is centralized as an enum, while user/admin entities are distinct beans.

• src/com/aman/service/UserService.java

• src/com/aman/servlets/UserRegServlet.java

• src/com/aman/constant/UserRole.java

4. Train catalog and admin management

The train subsystem owns listing, searching by route, fare/availability inquiries, and administrator CRUD-style schedule management. TrainService provides the business boundary; its implementation accesses persistence. Admin actions include add, update, cancel/delete, and view; user flows expose search and viewing.

• src/com/aman/service/TrainService.java

• src/com/aman/service/impl/TrainServiceImpl.java

• src/com/aman/beans/TrainBean.java

5. Booking lifecycle

Booking is a multi-step web flow: select a train, enter booking details, continue through payment handling, and persist a history record. Availability and cancellation are adjacent operations that must coordinate with train seat counts and booking history. The repository models booking/history separately from train data.

• src/com/aman/servlets/BookTrains.java

• src/com/aman/servlets/BookTrainPayment.java

• src/com/aman/service/impl/BookingServiceImpl.java

6. Persistence and data model

JDBC is the sole persistence integration. DBUtil reads connection configuration from src/application.properties and connects to the configured MySQL trainbook database. Core tables/entities are admin, customer, train, and history; booking identity/history uses transaction IDs.

• src/com/aman/utility/DBUtil.java

• src/com/aman/beans/BookingDetails.java

• src/com/aman/beans/HistoryBean.java

The web archive also contains WebContent/WEB-INF/lib/ojdbc8.jar, but the documented runtime database is MySQL; this driver is potentially legacy or unused.

7. Operational boundaries

The application depends on JDK 8, Apache Tomcat 9, Maven packaging, and a reachable MySQL instance. It has no REST/API tier or separate frontend runtime: browser HTML forms call servlet endpoints directly, servlets invoke services, services use JDBC, and outcomes return users to HTML pages or the error route.

• pom.xml

• WebContent/WEB-INF/web.xml

• src/com/aman/beans/TrainException.java