How juan-beltran0518/arepserverarchitectures works
Project type and purpose
• This is a lightweight, full-stack Java web server with a custom IoC (Inversion of Control) framework.
• Purpose: serve static assets (HTML/JS/CSS/images) and dynamic content via annotated POJO controllers using reflection.
File structure
• Top level:
· pom.xml + run.sh – build and startup scripts (Maven build).
· src/main/java/com/edu/esuelaing/arep/ – core packages:
– annotations/ – custom annotations (@RestController, @GetMapping, etc.).
– controllers/ – GreetingController, HelloController (business logic).
– ioc/ – BeanContainer, ReflectionLoader, MicroSpringBoot (IoC container & bootstrap).
– SimpleHttpServer, Request, RouteHandler, Main – HTTP server core + request routing.
· src/main/resources/public/ – static assets (index.html, app.js, style.css, images).
· src/test – unit tests for IoC and HTTP server.
README for additional insights
• Confirms:
• serves HTML and PNG, handles non-concurrent requests
• custom IoC container loads annotated classes by reflection
• routing defined by @GetMapping/@PostMapping
• No external DB; purely in-memory and file resources.