codes-spring converts a reusable Codes ProblemType into Spring Framework's native ProblemDetail.
dependencies {
implementation("io.github.aalsanie:codes-spring:0.4.0")
}The application supplies Spring Web. codes-spring does not impose a Spring Framework version transitively.
final class OrderProblems {
static final ProblemType ORDER_NOT_FOUND = ProblemType.of(
URI.create("https://api.example.com/problems/order-not-found"),
404,
"Order not found"
);
private OrderProblems() {
}
}ProblemDetail problem = ProblemDetails.forType(
OrderProblems.ORDER_NOT_FOUND
);For an occurrence-specific detail:
ProblemDetail problem = ProblemDetails.forTypeAndDetail(
OrderProblems.ORDER_NOT_FOUND,
"Order o-123 was not found."
);The bridge sets only type, status, title, and the explicitly supplied detail.
Do not populate detail from exception.getMessage() unless that message was explicitly designed for public API consumption. Internal exception text can expose implementation details, identifiers, or other sensitive information.
The bridge does not set the request-specific instance, add extension properties, map exceptions, or register controller advice.
Different internal exceptions can intentionally expose the same public problem type:
@ExceptionHandler(OrderNotFoundException.class)
ProblemDetail handleOrderNotFound(OrderNotFoundException ex) {
return ProblemDetails.forTypeAndDetail(
OrderProblems.ORDER_NOT_FOUND,
"Order " + ex.orderId() + " was not found."
);
}
@ExceptionHandler(ArchivedOrderNotFoundException.class)
ProblemDetail handleArchivedOrderNotFound(ArchivedOrderNotFoundException ex) {
return ProblemDetails.forTypeAndDetail(
OrderProblems.ORDER_NOT_FOUND,
"Archived order " + ex.orderId() + " was not found."
);
}Spring remains responsible for rendering the ProblemDetail through MVC or WebFlux.