How hoon105204/waggleproject works
Project type and purpose
• This is a monolithic full-stack web application built on Spring Boot, using JSP for the view layer, Spring MVC for request handling, MyBatis (mappers) for data access, and a relational database at the persistence layer.
• Purpose: “Waggle” lets users request in-person property visits (real estate) from other users, share details via chat, and fetch external property data via crawlers and OCR.
File structure
• Top-level:
• Servers/… – Eclipse/Tomcat server configs
• Waggle/ and Waggle2/ – two nearly identical Maven Spring Boot projects
• Waggle/src/main/java/com/probee/waggle:
• model/component – crawler (JsoupCrawler, SeleniumCrawler), OCR, FileSaver, security & web config
• model/controller – HTTP controllers (BoardController, ChatController, ChatbotController, MapController, etc.) + WebSocketConfig
• model/service – service interfaces & implementations
• model/mapper – MyBatis mapper interfaces for DB CRUD
• model/dto – data-transfer objects for request/response
• Waggle/src/main/webapp/WEB-INF/views – JSP pages for each feature
• static resources – CSS, images, CSV data
• application.properties – DB & security configuration