How sebastiansierra15/invehin works
Project type and purpose
• This is a full-stack Java web application (INVEHIN) for clothing store sales and inventory management.
• It uses JSP as the view layer, Servlets as controllers, Java classes for business logic and data access, and a MySQL database.
File structure
• Top-level “src/java” breaks into packages:
• Entidades – domain/model classes & DB connection
• Interfaces – DAO/service interface definitions
• Logica – business/service implementations
• Utils – reporting helpers (Excel/PDF generators)
• servlets – HTTP controllers
• “web” (and its build/web counterpart) holds static assets (images, components) and JSP views under “Views”.
• “WEB-INF/lib” contains third-party JARs (JDBC driver, Apache POI, iTextPDF, Gson, Commons libs, Log4j).
• “sql/DB_INVEHIN.sql” defines the schema.
• Build artifacts (build.xml, nbproject) reflect an Ant+NetBeans setup, producing a WAR for Tomcat.
README for additional insights
• Confirms Java 21, JSP/Servlet, Tomcat 10+, MySQL 8, JDBC, Apache POI & iTextPDF.
• Key modules: user management, sales, inventory, orders, reports.
a. Main components
• Browser (User Interface)
• Web Server & Servlet Container (Apache Tomcat)
• View Layer (JSP pages + static assets)
• Controller Layer (Servlet classes)
• Service/Business Layer (Logica package)
• Data Access Layer (Entidades + Interfaces using JDBC)
• MySQL Database
• Reporting Subsystem (Utils + Apache POI/iText)
• External Libraries (Log4j, Gson, Commons, MySQL Connector)
b. Relationships & interactions
1. User → HTTP Request → JSP (view) or directly to Servlet
2. Servlet reads request, invokes service in Logica
3. Service uses DAO interfaces (Interfaces) and Entities (Entidades) to perform JDBC operations
4. JDBC communicates with MySQL DB
5. Service returns data to Servlet → JSP renders response
6. For report endpoints, service delegates to Utils which uses Apache POI/iText to generate Excel/PDF
c. Architectural patterns & design principles
• MVC separation: JSP = View, Servlets = Controller, Logica = Model/Service
• DAO pattern: Interfaces define contracts, Entities represent tables, Logica implements business rules
• Layered architecture: clear boundaries between presentation, business, and data layers
• Reusable utility components for reporting
d. Key technologies/frameworks
• Java Servlets & JSP (Controller + View)
• MySQL via JDBC (Data persistence)
• Apache Tomcat (Servlet container)
• Apache POI & iTextPDF (report generation)
• Log4j, Gson, Apache Commons (extras)
Elements
• Labels: “Browser”, “Tomcat Container”, “JSP Views”, “Servlet Controllers”, “Service Layer”, “DAO Layer”, “MySQL DB”, “Reporting Utils”.
→ HTTP flow (Browser → JSP/Servlet → Browser)
→ Method calls (Servlet → Service → DAO → DB)
→ File generation (Service → Utils → PDF/Excel)
• Rounded rectangles for UI components (JSP, static assets) in blue
• Rectangles for controllers (Servlets) in green
• Rectangles for services (Logica) in orange