使用@PathVariable遇500错误，@RestController查询参数处理失效求助

Hey there, let's work through your two controller problems step by step—they're likely tied to mix-ups in how Spring handles path variables vs query parameters, plus some hidden binding or exception issues.

Problem 1: @PathVariable Throwing HttpServerErrorException: 500 null #

First up, that 500 error with @PathVariable almost always comes from a mismatch between your request URL and how you've defined the path variable in your controller. Here's what to check:

• Did you define the path placeholder in your @RequestMapping?
  If your method uses @PathVariable("latitude"), your request mapping needs to include that variable in the path, like /foo/{latitude}. If you just have /foo, Spring can't find the path variable to bind, which triggers a 500.

• Is there a type mismatch?
  If your path variable is a decimal (like 15.12345) but you're trying to bind it to an int instead of a Double or BigDecimal, Spring will throw a type conversion exception under the hood. Always match the parameter type to the data you're expecting.

• Are you handling optional path variables?
  If the path variable isn't required, add required = false to the @PathVariable annotation. Without this, if the URL doesn't include the variable, Spring will throw an error.

• Log the details!
  You're already using LogManager—add a debug log at the start of your controller method to print the path variable value, or set up a global exception handler to capture the full stack trace. That "null" in the 500 message is useless; the stack trace will tell you exactly what's breaking.

Example of a working @PathVariable setup:

@RequestMapping(value = "/foo/{latitude}", method = RequestMethod.GET)
public List<GooglePlace> getPlacesByLatitude(@PathVariable("latitude") Double latitude) {
    LOGGER.debug("Processing request with latitude: {}", latitude);
    return googlePlaceService.getPlaces(latitude);
}

Problem 2: GET Request with Query Params (/foo?latitude=15.12345) Not Working #

This is a common mix-up: @PathVariable is for path segments (like /foo/15.12345), but query parameters (the ?key=value part) need @RequestParam instead. Here's how to fix it, whether you need single or multiple parameters:

Option 1: Individual @RequestParam Annotations #

This is straightforward for a few parameters, and lets you mark them as optional if needed:

@RequestMapping(value = "/foo", method = RequestMethod.GET)
public List<GooglePlace> getPlaces(
        @RequestParam(value = "latitude", required = false) Double latitude,
        @RequestParam(value = "longitude", required = false) Double longitude) {
    LOGGER.debug("Received query params - Latitude: {}, Longitude: {}", latitude, longitude);
    
    // Handle different parameter combinations
    if (latitude != null && longitude != null) {
        return googlePlaceService.getPlacesByLatLng(latitude, longitude);
    } else if (latitude != null) {
        return googlePlaceService.getPlacesByLatitude(latitude);
    }
    // Add fallback logic for no parameters if needed
    return Collections.emptyList();
}

Option 2: Use a DTO for Multiple Parameters #

If you have lots of query parameters, wrapping them in a Data Transfer Object (DTO) keeps your controller method clean. Spring will automatically bind the query params to the DTO's fields:

// First, create the DTO class
public class PlaceQueryParams {
    private Double latitude;
    private Double longitude;
    // Add other parameters (radius, place type, etc.) as needed
    // Don't forget getters and setters!
    public Double getLatitude() { return latitude; }
    public void setLatitude(Double latitude) { this.latitude = latitude; }
    public Double getLongitude() { return longitude; }
    public void setLongitude(Double longitude) { this.longitude = longitude; }
}

// Then update your controller method
@RequestMapping(value = "/foo", method = RequestMethod.GET)
public List<GooglePlace> getPlaces(PlaceQueryParams params) {
    LOGGER.debug("Received query params: {}", params);
    return googlePlaceService.getPlaces(params);
}

Bonus Checks for Query Params #

• Check for uncaught exceptions in your service layer: If GooglePlaceService throws an exception that's not handled, it'll bubble up as a 500 error, making it look like the controller can't process the request. Wrap service calls in try-catch blocks or use a global exception handler.
• Enable debug logging for Spring Web: Add logging.level.org.springframework.web=DEBUG to your application.properties or application.yml. This will print detailed logs about parameter binding, so you can see if a query param is being ignored or causing a bind failure.

Quick Recap #

• Use @PathVariable for variables in the URL path (e.g., /foo/{id})
• Use @RequestParam for query parameters (e.g., /foo?id=123)
• Always check for type mismatches and uncaught exceptions when troubleshooting 500 errors
• Logging is your best friend—don't rely on generic error messages!

内容的提问来源于stack exchange，提问作者Stefan Falk