How jallamas/gestion-hermandad works
Main Components
• Client / Browser: The user interface, which is implemented using Thymeleaf templates (located in the “templates” directory) along with static assets (CSS, JavaScript, images in “static”).
• Web Server / Application: A Spring Boot application built with Maven (pom.xml, Maven wrapper files). This component includes several layers:
• Presentation Layer: Controllers (e.g., HermanoController, WebController, PapeletaSitioAdminController) that handle HTTP requests and drive the UI.
• Service Layer: Service classes (e.g., HermanoServicio, HermanoHistoricoServicio) that encapsulate the business logic.
• Persistence / Repository Layer: Repository interfaces (e.g., HermanoRepository, PuestoRepository) to interact with the database.
• Model Layer: Domain entities (e.g., Hermano, HermanoHistorico, HermanoProvisional) representing your data.
• Configuration & Security: Configuration classes such as MvcConfig and SecurityConfig along with UserDetailsServiceImpl, indicating use of Spring Security.
• Database: An embedded or file-based database (the “db” folder contains files like basededatos.mv.db) that stores the application’s data.
• Testing Frameworks: Test packages for unit and integration tests (located in “src/test”), ensuring application robustness.
Representing Relationships and Interactions
• Browser/client making HTTP requests to the Controller layer in the web server.
• Controllers forward requests to the respective Service layer components where business rules are applied.
• Service classes then interact with the Repository layer to perform CRUD operations on the Database.
• A separate path for security where requests are intercepted and validated by SecurityConfig/UserDetailsServiceImpl.
• Optionally, note the build and deployment aspects (e.g., Maven build process) as supportive infrastructure.
Architectural Patterns and Technologies
• MVC Pattern: Clearly note the separation of concerns with Controllers (Presentation), Services (Business Logic), and Repositories (Data Persistence).
• Spring Boot: Indicate that the backend is powered by Spring Boot, which simplifies dependency injection and configuration.
• Thymeleaf: Mark this as the view/template engine used for composing dynamic HTML pages.
• Spring Security: Emphasize the security configuration aspect providing authentication/authorization.
• Embedded Database: Make a note that the project uses either an embedded H2 or similar database (as evidenced from the “db” directory).