From 302c24aaa85a3863c5200290e39b0ae3e18d1c08 Mon Sep 17 00:00:00 2001 From: Linor Dolev Date: Thu, 14 Mar 2024 23:17:59 +0200 Subject: [PATCH] Fix default strategy description of ProblemDetail error codes See gh-32446 --- .../ROOT/pages/web/webmvc/mvc-ann-rest-exceptions.adoc | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/framework-docs/modules/ROOT/pages/web/webmvc/mvc-ann-rest-exceptions.adoc b/framework-docs/modules/ROOT/pages/web/webmvc/mvc-ann-rest-exceptions.adoc index 66bfbc0e76..5dc7aac21d 100644 --- a/framework-docs/modules/ROOT/pages/web/webmvc/mvc-ann-rest-exceptions.adoc +++ b/framework-docs/modules/ROOT/pages/web/webmvc/mvc-ann-rest-exceptions.adoc @@ -74,14 +74,13 @@ It is a common requirement to customize and internationalize error response deta It is also good practice to customize the problem details for Spring MVC exceptions to avoid revealing implementation details. This section describes the support for that. -An `ErrorResponse` exposes message codes for "type", "title", and "detail", as well as -message code arguments for the "detail" field. `ResponseEntityExceptionHandler` resolves +An `ErrorResponse` exposes message codes for "type" and "title". `ResponseEntityExceptionHandler` resolves these through a xref:core/beans/context-introduction.adoc#context-functionality-messagesource[MessageSource] and updates the corresponding `ProblemDetail` fields accordingly. The default strategy for message codes follows the pattern: -`problemDetail.[type|title|detail].[fully qualified exception class name]` +`problemDetail.[type|title].[fully qualified exception class name]` An `ErrorResponse` may expose more than one message code, typically adding a suffix to the default message code. The table below lists message codes, and arguments for