How haazzero/finalproject_homey works
Project Type and Purpose
• This is a monolithic, full-stack web application built on Spring MVC with MyBatis and Oracle.
• It serves as an interior-construction company’s customer portal: users browse services, submit requests, review projects, manage profiles, and administrators manage content.
High-Level Architectural Components
a. Client Tier
• Web browsers requesting JSP pages and static assets (JS/CSS/images)
b. Web/Application Server
• Apache Tomcat hosting the Spring MVC application
• Spring’s DispatcherServlet (front controller)
• Spring Security filter chain for authentication/authorization
c. Presentation Layer
• Controllers (org.homey.controller.*)
• JSP view layer under WEB-INF/views, resolved by InternalResourceViewResolver
d. Service Layer
• org.homey.service.* interfaces and their Impl classes
• Business logic, transaction boundaries, calls to persistence or external services
e. Persistence Layer
• MyBatis mappers (interfaces + XML in resources/org/homey/mapper)
• Data Transfer / Value Objects (VOs in org.homey.domain)
• Oracle Database accessed via JDBC/MyBatis
f. External Services
• EmailService invoking SMTP server
• (Potential future REST or third-party integrations)
Architectural Patterns & Principles
• MVC pattern: clear separation of concerns
• Layered architecture: presentation / service / persistence
• Dependency Injection (Spring) for controllers, services, mappers
• Transaction management at service layer
• Security via custom handlers and UserDetailsService