How engineeringsebastian-s/sudoku works
Project type and purpose
• This is a full-stack web application (Sudoku game) built with Spring Boot (Java) using an MVC pattern. It serves HTML pages (Thymeleaf or similar templating) and static assets (CSS) to the browser. It also configures an RMI server for remote Sudoku service access.
File structure
• Top-level artifacts:
• pom.xml and Maven wrapper for build and dependency management
• src/main/java/poli/engineering/sudoku: Java code, split into
– Config (RmiServerConfig.java)
– Controller (MenuController.java, SudokuController.java)
– Service (ISudokuService.java, SudokuService.java)
– Application entry point (SudokuApplication.java)
• src/main/resources:
– application.yml (Spring Boot configuration)
– static/: CSS files (board.css, main.css, menu.css, root.css)
– templates/: HTML views (menu.html, board.html)
• src/test: basic Spring Boot test class (SudokuApplicationTests.java)
README for additional insights
• The README only shows “# Sudoku,” confirming the core purpose: serving a Sudoku game application.
Elements
• Clear component labels (e.g., “SudokuController,” “SudokuService,” “RmiServerConfig”)
• HTTP requests/responses between Browser ↔ Controllers
• Method calls between Controllers → Service → (domain logic)
• RMI calls between External Client ↔ RMI Server
• Rectangles for components (controllers, services)