How namnguyen1409/assignment works
Project type and purpose
• This is a monolithic, full‐stack Java web application (packaged as a WAR) built with Spring MVC, Spring Security, Spring Data JPA/Hibernate, JSP views, and static resources.
• From the packages (com.assignment.models.entities.shop, api, controllers/role/user, service), it appears to be an “all-in-one” e-commerce assignment platform with user authentication (including OAuth2 and 2FA), buying, selling, and an e-wallet subsystem.
File structure
Top‐level directories:
• python/ – utility scripts for enum/repo code generation and SQL loads (external preprocessing).
• src/main/java/com/assignment/ – Java source split into subpackages:
– api/ – REST‐style endpoints (CategoryAPI, UserAPI, etc.)
– controllers/ – MVC controllers (AdminController, HomeController, auth, role/user sub‐controllers)
– filter/ – servlet filters (AntiBotFilter, JwtAuthenticationFilter, etc.)
– security/ – custom UserDetails, JWT providers, OAuth2 client config
– service/ – business logic (EmailService, ImageUploadService, TOTPService, QRCodeService…)
– models/entities & models/repositories – JPA entities and Spring Data repositories organized by domain (auth, ewallet, shop, location).
– validation/ – custom validation annotations and validators.
– config/ – Spring configuration (DispatcherServlet initializer, Web MVC config, data initialization).
• src/main/resources – persistence config, properties, SQL DDL/data scripts.
• src/main/webapp – JSP view templates (under WEB‐INF/views), static assets (CSS, JS, images, TinyMCE editor, videos).
README
• Bare-bones description: “project for all in one service.” We infer it provides a unified platform for authentication (login, OAuth2, TOTP), catalog/category management, user roles (buyer, seller, admin), purchase workflow, e-wallet operations, and file uploads (images/videos).