How danygeier/sistema-de-gestion-de-tickets works
This repository is a Java ticket-management backend: clients create tickets, and employees can respond to them; tickets can then be searched and managed by status, priority, type, user, and date. The sampled business layer validates ticket creation and delegates to DAOs, which persist through Hibernate. Responses have a separate business/DAO path and can update ticket state. The model also includes users, roles, and ticket classification entities. No README or user interface is present; links to database infrastructure are limited by the sampled evidence.
Main entry points: Ticket.java Ticket · TicketABM.java Ticket management · RespuestaDao.java Response queries and writes · TicketDao.java Ticket queries and writes
Components 17
Ticket workflow
- Ticket management
Gestion-Tickets/src/negocio/TicketABM.java - Ticket queries and writes
Gestion-Tickets/src/dao/TicketDao.java
Response workflow
- Response management
Gestion-Tickets/src/negocio/RespuestaABM.java - Response queries and writes
Gestion-Tickets/src/dao/RespuestaDao.java
Domain model
- Ticket
Gestion-Tickets/src/datos/Ticket.java - Response
Gestion-Tickets/src/datos/Respuesta.java - User and role
Gestion-Tickets/src/datos/Usuario.java - Person
Gestion-Tickets/src/datos/Persona.java - Status
Gestion-Tickets/src/datos/Estado.java - Priority
Gestion-Tickets/src/datos/Prioridad.java - Category
Gestion-Tickets/src/datos/Categoria.java - Ticket type
Gestion-Tickets/src/datos/Tipo.java - Role
Gestion-Tickets/src/datos/Rol.java
Persistence
- Hibernate sessions
Gestion-Tickets/src/dao/HibernateUtil.java - MySQL database
Gestion-Tickets/bd-gestion-tickets.sql
Other components
- Client
- Employee
Connections 20
- Client → Ticket management: creates tickets
- Employee → Response management: manages responses
- Ticket management → Ticket queries and writes: delegates ticket operations
Gestion-Tickets/src/negocio/TicketABM.java - Ticket management → Status: loads open status
Gestion-Tickets/src/negocio/TicketABM.java - Ticket management → Role: checks client role
Gestion-Tickets/src/negocio/TicketABM.java - Response management → Response queries and writes: delegates response operations
Gestion-Tickets/src/negocio/RespuestaABM.java - Ticket queries and writes → Ticket: queries and persists
Gestion-Tickets/src/dao/TicketDao.java - Response queries and writes → Response: queries and persists
Gestion-Tickets/src/dao/RespuestaDao.java - Response queries and writes → Ticket: updates ticket state
Gestion-Tickets/src/dao/RespuestaDao.java - Ticket → User and role: references
Gestion-Tickets/src/datos/Ticket.java - Ticket → Status: references
Gestion-Tickets/src/datos/Ticket.java - Ticket → Priority: references
Gestion-Tickets/src/datos/Ticket.java - Ticket → Category: references
Gestion-Tickets/src/datos/Ticket.java - Ticket → Ticket type: references
Gestion-Tickets/src/datos/Ticket.java - Ticket → Response: references
Gestion-Tickets/src/datos/Ticket.java - User and role → Person: extends
Gestion-Tickets/src/datos/Usuario.java - User and role → Role: references
Gestion-Tickets/src/datos/Usuario.java - Ticket queries and writes → Hibernate sessions: opens sessions
Gestion-Tickets/src/dao/TicketDao.java - Response queries and writes → Hibernate sessions: opens sessions
Gestion-Tickets/src/dao/RespuestaDao.java - Hibernate sessions → MySQL database: connects via ORM