Routing

Goal

This snapshot advances Ironclad Gazette by teaching you to organize page routes with Spring MVC controllers.

Every numbered folder is a complete app. Run this stage independently, then compare it with the previous folder.

Prerequisites

Use Java 17+, Maven, a terminal, and Docker for MySQL stages. You should recognize classes, annotations, and HTTP verbs.

Port 8080 must be free. Copy .env.example before starting database stages.

• Java 17 and Maven
• A code editor and terminal
• Docker from part 4 onward

Concepts

@GetMapping maps HTTP GET requests to controller methods. Route paths and return types both matter.

Keep controllers thin: accept input, delegate to repositories or services, and let Thymeleaf escape output by default.

Walkthrough

Add home, about, and health endpoints on dedicated controller methods.

Read the example, then open the matching snapshot. The repository includes the surrounding setup and error handling.

@GetMapping("/about")
public String about() {
  return "About Ironclad Gazette";
}

Run and verify

Enter 02-Routing, start MySQL when needed, copy .env.example, and run mvn spring-boot:run on port 8080.

Open http://127.0.0.1:8080. Watch the terminal for validation and database errors.

git clone https://github.com/michaeldunga1/fcc-spring-blog.git
cd fcc-spring-blog/02-Routing
cp .env.example .env
mvn spring-boot:run

Troubleshooting

A missing annotation or wrong path leaves routes undefined. Check both path and HTTP method.

Connection refused usually means Docker MySQL is stopped or the port is not 3308. For auth issues, confirm you are using email (not username) on the login form.

• Read the first error first
• Restart after environment changes
• Never commit .env or uploads

Try this

Add a /contact plain-text route.

Test a happy path and one invalid or unauthorized request.

• Make one small change
• Test it in the browser
• Compare with the next snapshot only after it works