Fix default strategy description of ProblemDetail error codes

See gh-32446
This commit is contained in:
Linor Dolev 2024-03-14 23:17:59 +02:00 committed by Stéphane Nicoll
parent 7357812b4e
commit 302c24aaa8
1 changed files with 2 additions and 3 deletions

View File

@ -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 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. 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 An `ErrorResponse` exposes message codes for "type" and "title". `ResponseEntityExceptionHandler` resolves
message code arguments for the "detail" field. `ResponseEntityExceptionHandler` resolves
these through a xref:core/beans/context-introduction.adoc#context-functionality-messagesource[MessageSource] these through a xref:core/beans/context-introduction.adoc#context-functionality-messagesource[MessageSource]
and updates the corresponding `ProblemDetail` fields accordingly. and updates the corresponding `ProblemDetail` fields accordingly.
The default strategy for message codes follows the pattern: 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 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 to the default message code. The table below lists message codes, and arguments for