How jimwu666/job-portal-project works
Project Type and Purpose
• This is a full-stack web application: a job portal where recruiters post/manage jobs and job seekers search, save, and apply.
• Backend: Java Spring Boot (MVC pattern), Spring Security, Spring Data JPA, Thymeleaf.
• Frontend: HTML/CSS/JS static assets (Bootstrap-like styling, Summernote rich text editor).
Main Components
a. Client Layer
• Web Browser (or Mobile WebView)
• Interacts via HTTP/HTTPS
b. Presentation Layer (Frontend)
• Static Resources: CSS, JS (main.js, vendor, Summernote plugins)
• Templates: Thymeleaf HTML pages under src/main/resources/templates
c. Application Layer (Backend)
• Spring Boot App (JobportalApplication)
• Spring MVC DispatcherServlet → Controllers
– HomeController, JobPostActivityController, JobSeekerApplyController, etc.
• Spring Security Filter Chain
– WebSecurityConfig, CustomAuthenticationSuccessHandler
• Service Layer
– Business logic: JobPostActivityService, UsersService, etc.
• Data Access Layer
– Spring Data JPA Repositories
– Entities → Database tables
d. Persistence Layer
• Relational Database (MySQL/Postgres)
• Tables created via provided SQL scripts
e. File Storage
• Local file system (or blob storage) for profile photos, resumes
• Utility classes: FileUploadUtil, FileDownloadUtil
f. External/Third-Party
• (Optional) Email service for notifications
• (Optional) Cloud storage if used in production
Relationships and Data Flow
• Client → HTTP Request → Spring Security → DispatcherServlet
• DispatcherServlet → Chooses Controller (based on URL mapping)
• Controller → calls Service → calls Repository → queries DB
• Service returns data to Controller → Controller returns Model + View
• Thymeleaf renders View + Model → HTML → Client
• File uploads: Controller → FileUploadUtil writes to storage → DB records file path
• File downloads: Controller → FileDownloadUtil reads file → streams to client
Architectural Patterns & Design Principles
• Layered architecture: Presentation → Controller → Service → Repository → Database
• MVC (Model-View-Controller)
• Spring Security for authentication/authorization
• Dependency Injection / Inversion of Control
• Separation of concerns (e.g., CustomUserDetailsService handles user lookup)