How heinzdanner/java-ecosystem-exception-task works
This is a small in-memory student registry. The demonstrated workflow starts in Main, builds a Student, and asks StudentService to assign an ID and save it through StudentRepo. The repository keeps records in a map and also exposes listing and ID lookup; no callers for those read operations are shown. The graph reflects the supplied source excerpts; the README is empty.
Main entry points: StudentService.java Student service · StudentRepo.java Student repository · Student.java Student record · Main.java Main
Components 5
Application flow
- Main
src/main/java/Main.java - Student service
src/main/java/StudentService.java
Student data
- Student record
src/main/java/Student.java - Student repository
src/main/java/StudentRepo.java - Student map
src/main/java/StudentRepo.java
Connections 6
- Main → Student service: adds student
src/main/java/Main.java - Main → Student record: builds
src/main/java/Main.java - Student service → Student record: assigns ID
src/main/java/StudentService.java - Student service → Student repository: delegates storage
src/main/java/StudentService.java - Student repository → Student map: reads and writes
src/main/java/StudentRepo.java - Student repository → Student record: stores records
src/main/java/StudentRepo.java