ReservasController

​

Overview

​

Methods

​

ListarReservas

public ActionResult ListarReservas()

​

HTTP Method

​

Route

​

Returns

• Success (200): Returns a view with List<CE_Reservas> containing all reservations
• Error: Returns a view with an empty list and sets error message in TempData["ErrorMessage"]

​

Response Model

CE_Reservas {
  int IdReserva
  int IdCancha
  int IdCliente
  int IdUsuario
  DateTime FechaReserva
  TimeSpan HoraInicio
  TimeSpan HoraFin
  string NombreCliente
  string NombreCancha
  string Comentario
  bool Estado
}

​

Error Handling

• Validates ModelState before processing
• Catches exceptions and stores error message in TempData
• Returns empty list on error instead of throwing

​

Usage Example

// GET /Reservas/ListarReservas
// Returns view with list of all reservations

​

Source

​

InsertarReservas (GET)

public ActionResult InsertarReservas()

​

HTTP Method

​

Route

​

Returns

• Reserva: Empty CE_Reservas object
• ListaClientes: List of all available clients
• ListaCanchas: List of all available sports fields

​

View Model

ReservaViewModel {
  CE_Reservas Reserva
  List<CE_Clientes> ListaClientes
  List<CE_Canchas> ListaCanchas
}

​

Usage Example

// GET /Reservas/InsertarReservas
// Returns view with form and dropdown data for clients and canchas

​

Notes

• Initializes empty CE_Reservas object to prevent null reference errors
• Loads client and cancha lists from business layer
• Uses ViewModel pattern to pass multiple data collections to view

​

Source

​

InsertarReservas (POST)

[HttpPost]
public ActionResult InsertarReservas(ReservaViewModel reservas)

​

HTTP Method

​

Route

​

Parameters

​

Returns

• Success (302): Redirects to ListarReservas action
• Error (404): Reserva object is null - “No se encontro el modelo”
• Error (500): Exception during creation - “Error al agregar la reserva: “

​

Error Responses

"No se encontro el modelo"

"Error al agregar la reserva: {error message}"

​

Usage Example

// POST /Reservas/InsertarReservas
// Content-Type: application/x-www-form-urlencoded

var viewModel = new ReservaViewModel {
    Reserva = new CE_Reservas {
        IdCancha = 1,
        IdCliente = 5,
        IdUsuario = 1,
        FechaReserva = DateTime.Parse("2026-03-10"),
        HoraInicio = TimeSpan.Parse("14:00"),
        HoraFin = TimeSpan.Parse("16:00"),
        Comentario = "Torneo interno",
        Estado = true
    }
};

// On success: Redirects to /Reservas/ListarReservas

​

Notes

• Validates that reservas.Reserva is not null instead of using ModelState.IsValid
• Previous implementation using CE_Reservas directly is commented out (lines 51-70)
• Uses ViewModel approach for better integration with dropdown-based forms

​

Source

​

Actualizar (GET)

[HttpGet]
public ActionResult Actualizar(int id)

​

HTTP Method

​

Route

​

Parameters

​

Returns

• Success (200): Returns view with the CE_Reservas object
• Error (404): Reservation not found - “No se pudo actualizar el cliente con el id: “

​

Error Responses

"No se pudo actualizar el cliente con el id: {id}"

​

Usage Example

// GET /Reservas/Actualizar/15
// Returns view with reservation data for ID 15

​

Notes

• Error message references “cliente” instead of “reserva” (copy-paste issue)

​

Source

​

Actualizar (POST)

public ActionResult Actualizar(CE_Reservas reservas)

​

HTTP Method

​

Route

​

Parameters

​

Returns

• Success (302): Redirects to ListarReservas action
• Error (500): Exception during update - “Error al actualizar la cancha: “

​

Error Responses

"Error al actualizar la cancha: {error message}"

​

Usage Example

// POST /Reservas/Actualizar
// Content-Type: application/x-www-form-urlencoded

var reserva = new CE_Reservas {
    IdReserva = 15,
    IdCancha = 2,
    IdCliente = 5,
    IdUsuario = 1,
    FechaReserva = DateTime.Parse("2026-03-12"),
    HoraInicio = TimeSpan.Parse("15:00"),
    HoraFin = TimeSpan.Parse("17:00"),
    Comentario = "Cambio de horario",
    Estado = true
};

// On success: Redirects to /Reservas/ListarReservas

​

Notes

• The method updates the reservation regardless of ModelState.IsValid status (lines 110-116)
• Both validation paths lead to the same update operation
• Error message references “cancha” instead of “reserva” (copy-paste issue)
• Missing [HttpPost] attribute but behaves as POST method

​

Source

​

Eliminar

public ActionResult Eliminar(int id)

​

HTTP Method

​

Route

​

Parameters

​

Returns

• Success (302): Redirects to ListarReservas action
• Error (500): Exception during deletion - “Error al eliminar la reserva: “

​

Error Responses

"Error al eliminar la reserva: {error message}"

​

Usage Example

// POST /Reservas/Eliminar
// Form data: id=15

// On success: Redirects to /Reservas/ListarReservas

​

Notes

• Includes try-catch error handling
• Returns appropriate error message to user
• Missing [HttpPost] attribute

​

Source

​

BuscarReservaNombre (GET)

[HttpGet]
public ActionResult BuscarReservaNombre()

​

HTTP Method

​

Route

​

Returns

​

Usage Example

// GET /Reservas/BuscarReservaNombre
// Displays the search form

​

Source

​

BuscarReservaNombre (POST)

[HttpPost]
public ActionResult BuscarReservaNombre(string BuscarReservaNombre)

​

HTTP Method

​

Route

​

Parameters

​

Returns

• All reservations if search term is empty
• Filtered reservations matching the client name if search term provided

​

Usage Example

// POST /Reservas/BuscarReservaNombre
// Form data: BuscarReservaNombre="Juan"

// Returns view with all reservations for clients named "Juan"

​

Search Behavior

// Empty search term
BuscarReservaNombre = ""
// Result: Returns all reservations

// With search term
BuscarReservaNombre = "Juan Pérez"
// Result: Returns reservations where NombreCliente contains "Juan Pérez"

​

Notes

• No error handling implemented
• Returns view (not redirect) to maintain search state
• Searches by client name using Reservas.ListarNombre()

​

Source

​

Dependencies

• Business Layer:
  • CN_Reservas from capa_negocio
  • CN_Clientes from capa_negocio
  • CN_Canchas from capa_negocio
• Entity Layer:
  • CE_Reservas from capa_entidad
  • CE_Clientes from capa_entidad
  • CE_Canchas from capa_entidad
• View Models: ReservaViewModel from capa_presentacion.Models
• Framework: ASP.NET Core MVC

​

Error Handling Strategy

1. Model Validation: Checks ModelState.IsValid or null validation before processing requests
2. Try-Catch Blocks: Wraps operations in exception handlers (most methods)
3. User Feedback: Uses TempData for error messages in views
4. Status Codes: Returns appropriate HTTP status codes (404, 500)
5. Graceful Degradation: Returns empty lists instead of error pages when listing fails

​

Design Patterns

• ViewModel Pattern: Uses ReservaViewModel to combine multiple entities for form dropdowns
• Repository Pattern: Delegates data access to business layer (CN_Reservas)
• PRG Pattern: Post-Redirect-Get pattern after successful mutations

​

Known Issues

• Error Messages: Several methods reference wrong entity types in error messages (“cliente”, “cancha” instead of “reserva”)
• Missing Attributes: Some POST methods missing [HttpPost] attribute
• Inconsistent Validation: Mix of ModelState.IsValid checks and null checks
• Redundant Code: Update methods execute regardless of validation result (lines 110-116)