How mirijamarc/eval_mai works
Project type and purpose
• From the file tree and README, this is a Java Spring Boot monolithic web application (“Eval_Mai”) that manages “devis” (quotes), maisons, travaux, finitions, paiements, etc., with distinct admin and client roles. It uses server-side MVC rendering via Thymeleaf templates, static resources (JS/CSS), CSV/Excel import-export, and a relational database (populated via the utilitaire/sql scripts).
File structure
• Top‐level build: pom.xml, Maven wrapper.
• src/main/java/com/evaluation/Eval:
• controller/… – Spring MVC controllers (CSVImportController, DevisController, admin and client subpackages)
• dto/… – Data Transfer Objects for web layer
• entity/… – JPA/Hibernate entities & view‐mapping classes
• repository/… – Spring Data JPA repositories for CRUD and custom queries
• security/… – custom interceptor, role enum, WebMvcConfig, NoSession exception
• util/… – CSV/Excel import‐export utilities, constants, error handling
• src/main/resources:
• application.properties – configuration (e.g., DB connection)
• static/… – CSS, JS, vendor libs, uploads
• templates/… – Thymeleaf HTML views: layouts, pages (admin/client), error, PDF exports
• utilitaire/sql/… – SQL scripts for schema, data, views for different contexts (construction, cinepax, f1)
README
• The README only contains the project title. Use the file structure to infer architecture: classical Spring Boot MVC monolith with layered approach (Controller → DTO → Entity → Repository → DB) plus utilities and security.
Final advice
• Both synchronous flows (web requests) and asynchronous or batch flows (CSV import).
• Security interceptor sits on the incoming HTTP path before controllers.
• Don’t omit static resources and template engine—they form the client‐side rendering component.
• Important configuration points (application.properties for DB connection, utilitaire/sql for schema).