How raghavulu111/reservation_system_train_ticket works
Project type and purpose
• This is a monolithic full-stack web application built on Java J2EE (Servlets + JDBC) with a static HTML/CSS/Bootstrap front-end and an Oracle relational database back-end.
• Purpose: Allow admins and users to view and manage train schedules, check availability, perform fare enquiries, book tickets, and manage user accounts.
File structure
• Top-level:
• pom.xml – Maven build descriptor
• WebContent/ – Static front-end assets (HTML, CSS, Bootstrap) and the web.xml deployment descriptor
• src/ – Java source tree
• Under src/:
• com.shashi.servlets – HTTP controllers handling incoming requests and dispatching to views
• com.shashi.service (and impl) – Business/service layer interfaces and implementations
• com.shashi.beans – Plain Old Java Objects (POJOs) modeling domain entities (User, Train, Booking, etc.)
• com.shashi.utility – Helpers for database connections (DBUtil) and common transformations
• com.shashi.constant – Application-wide constants (response codes, user roles)
• application.properties – Externalized configuration (e.g., DB URL/credentials)
• Deployment:
• WebContent/WEB-INF/lib – ojdbc8.jar for Oracle connectivity
• WebContent/WEB-INF/web.xml – Servlet mappings
Key insights from README
• Two actor types: Admin and User, each with a distinct set of use-cases
• Core functionalities: search/view trains, fare enquiry, seat availability, booking, history, profile management, payment gateway integration
• Technology stack: HTML/CSS/Bootstrap, Java Servlets, JDBC, Oracle SQL