How danieibazgc/retofutbol works
Project Type and Purpose
• This is a Java EE web application (MVC) built with NetBeans, JSP/JSTL for the view, servlets for controllers, a DAO layer for persistence, and MySQL as the backing store.
• It manages inventory, sales, customers, user roles, and reporting for a football‐jersey store (“RetoFutbol”).
File Structure Analysis
• Frontend (View):
• web/ (and build/web/): all JSP pages (index.jsp, login.jsp, clientes.jsp, productos.jsp, etc.), CSS under web/css/, images under web/img/, navigation fragments under web/navegador/.
• Controller Layer:
• src/java/Controlador/: servlet classes (srvLogin.java, srvCliente.java, srvProductos.java, etc.) that handle HTTP requests, coordinate business logic, and forward/redirect to JSPs.
• Model & Persistence:
• src/java/Modelo/: plain Java objects (Cliente.java, Producto.java, Venta.java, etc.).
• src/java/DAO/: Data Access Object classes (ClienteDAO.java, VentaDAO.java, etc.) plus Conexion.java for JDBC connection and Parametros.java for SQL parameters.
• Configuration & Build:
• web/META-INF/context.xml: resource definitions.
• build.xml and nbproject/: Ant build scripts and NetBeans project metadata.
Key Architectural Patterns
• MVC: Views (JSP) ←→ Controllers (Servlets) ←→ Models (Java beans) ←→ DAO (Persistence).
• DAO Pattern: Encapsulates all direct JDBC calls and SQL into DAO classes.
• Ant‐based Deployment: build.xml packages the WAR under build/web/.
Main Components
a. Clients (Browsers): Users interact via HTTP(S).
b. Web Server / Servlet Container: e.g., Tomcat running the WAR.
c. View Layer (JSP + CSS + JSTL):
• JSP pages under /WEB‐INF/views (in this project directly under web/).
d. Controller Layer (Servlets): one servlet per use‐case (Login, Cliente, Producto, Venta, etc.).
e. Service/Business Logic (if any): simple orchestration inside servlets and DAO.
f. DAO Layer: classes mapping to tables, handling CRUD via JDBC.
g. MySQL Database: tables for users, products, sales, clients, etc.
h. External Libraries:
• mysql-connector-j for JDBC driver
• jstl-1.2.jar for JSP tags
Interactions & Data Flow
1. Browser → HTTP Request → Servlet (e.g., /srvLogin)
2. Servlet invokes → DAO (e.g., UsuarioDAO.validate(...))
3. DAO opens → JDBC Connection → executes SQL on MySQL → maps ResultSet to Model object
4. Servlet stores data in request/session → forwards to → JSP View
5. JSP renders HTML/CSS → Browser
• A deployment node representing the servlet container and database server.