How deepa17621/eventmanagementapplication works
This is a console-based event booking management application. An admin creates and manages the service catalogue; a client signs up, selects services for an event, and can retrieve event details. MainApp presents the menus, while EventManagementController owns the workflow and delegates persistence to DAOs. The entity classes describe the stored records and their relationships. DAO-to-database links reflect the sampled JPA operations; other persistence configuration details were not inspected.
Main entry points: EventManagementController.java Workflow controller · persistence.xml JPA database · ClientEvent.java Client event · AdminDao.java Admin DAO
Components 15
Console entry
- Menu application
src/main/java/controller/MainApp.java
Booking workflows
- Workflow controller
src/main/java/controller/EventManagementController.java
Data access
- Admin DAO
src/main/java/dao/AdminDao.java - Client DAO
src/main/java/dao/ClientDao.java - Event DAO
src/main/java/dao/ClientEventDao.java - Event service DAO
src/main/java/dao/ClientServiceDao.java - Catalogue DAO
src/main/java/dao/ServiceDao.java - JPA database
src/main/resources/META-INF/persistence.xml
Domain records
- Admin record
src/main/java/dto/Admin.java - Client record
src/main/java/dto/Client.java - Client event
src/main/java/dto/ClientEvent.java - Event service
src/main/java/dto/ClientService.java - Catalogue service
src/main/java/dto/Service.java - Event types
src/main/java/dto/EventType.java
Other components
- Console user
Connections 25
- Console user → Menu application: uses menus
src/main/java/controller/MainApp.java - Menu application → Workflow controller: invokes workflows
src/main/java/controller/MainApp.java - Workflow controller → Admin DAO: manages admins
src/main/java/controller/EventManagementController.java - Workflow controller → Client DAO: saves clients
src/main/java/controller/EventManagementController.java - Workflow controller → Event DAO: updates events
src/main/java/controller/EventManagementController.java - Workflow controller → Event service DAO: saves event services
src/main/java/controller/EventManagementController.java - Workflow controller → Catalogue DAO: manages catalogue
src/main/java/controller/EventManagementController.java - Workflow controller → Event types: selects type
src/main/java/controller/EventManagementController.java - Workflow controller → Admin record: creates and checks
src/main/java/controller/EventManagementController.java - Workflow controller → Client record: signs up and checks
src/main/java/controller/EventManagementController.java - Workflow controller → Client event: creates and retrieves
src/main/java/controller/EventManagementController.java - Workflow controller → Event service: calculates and adds
src/main/java/controller/EventManagementController.java - Admin DAO → Admin record: persists admin
src/main/java/dao/AdminDao.java - Client DAO → Client record: persists client
src/main/java/dao/ClientDao.java - Event DAO → Client event: persists event
src/main/java/dao/ClientEventDao.java - Event service DAO → Event service: persists service
src/main/java/dao/ClientServiceDao.java - Catalogue DAO → Catalogue service: persists catalogue item
src/main/java/dao/ServiceDao.java - Admin DAO → JPA database: uses JPA
src/main/java/dao/AdminDao.java - Client DAO → JPA database: uses JPA
src/main/java/dao/ClientDao.java - Event DAO → JPA database: uses JPA
src/main/java/dao/ClientEventDao.java - Event service DAO → JPA database: uses JPA
src/main/java/dao/ClientServiceDao.java - Catalogue DAO → JPA database: uses JPA
src/main/java/dao/ServiceDao.java - Admin record → Catalogue service: owns services
src/main/java/dto/Admin.java - Client record → Client event: has events
src/main/java/dto/Client.java - Client event → Event service: contains services
src/main/java/dto/ClientEvent.java