How karanbastola84/college-care works
Project type and purpose
• From the file tree and the minimal README title “college-care-system,” we see a Java-based web application structured around Java Servlets, JSPs, Filters, Services, DTOs, and DAOs, packaged with Maven.
• It follows an MVC-style monolithic architecture to handle user registration, login, profile management, admin dashboard, password reset, account deletion, etc., backed by a relational database (schema.sql).
File structure
• Top-level artifacts: pom.xml (Maven), mvnw scripts (build), README.md.
• src/main/java/com/example/collegecaresystem/controller → all HTTP endpoints (Servlets).
• src/main/java/com/example/collegecaresystem/filter → request filters (AuthenticationFilter, AuthorizationFilter).
• src/main/java/com/example/collegecaresystem/service → business-logic services (AuthService, UserService).
• src/main/java/com/example/collegecaresystem/dto → data transfer objects (UserDTO).
• src/main/java/com/example/collegecaresystem/utils → helper classes (DBConnectionUtil, PasswordHash).
• src/main/java/model → persistence layer (UserDAO, Contact, Report, User).
• src/main/resources/schema.sql → DB schema.
• src/main/webapp/WEB-INF/view → JSPs organized by admin vs. user views.
• Configuration: web.xml for servlet and filter mappings; static assets under assets/css.
README
• The README only gives the project name; no extra architecture hints. We rely on conventions and file-layout patterns.