Uses of Class
org.springframework.http.ProblemDetail
Package
Description
Contains a basic abstraction over client/server-side HTTP.
Common, generic interfaces that define minimal boundary points
between Spring's web infrastructure and other framework modules.
Provides web-specific data binding functionality.
Support for asynchronous request processing.
Support classes for the multipart resolution framework.
Infrastructure for annotation-based handler method processing.
Provides servlets that integrate with the application context
infrastructure, and the core interfaces and classes for the
Spring web MVC framework.
MVC infrastructure for annotation-based handler method processing, building on the
org.springframework.web.method.annotation
package.-
Uses of ProblemDetail in org.springframework.http
Modifier and TypeMethodDescriptionstatic ProblemDetail
ProblemDetail.forStatus
(int status) Create aProblemDetail
instance with the given status value.static ProblemDetail
ProblemDetail.forStatus
(HttpStatusCode status) Create aProblemDetail
instance with the given status code.static ProblemDetail
ProblemDetail.forStatusAndDetail
(HttpStatusCode status, String detail) Create aProblemDetail
instance with the given status and detail.Modifier and TypeMethodDescriptionstatic ResponseEntity.HeadersBuilder<?>
ResponseEntity.of
(ProblemDetail body) Create a newResponseEntity.HeadersBuilder
with its status set togetStatus()
and its body is set toProblemDetail
.ModifierConstructorDescriptionprotected
ProblemDetail
(ProblemDetail other) Copy constructor that a subclass can use to re-create and extend aProblemDetail
with additional properties. -
Uses of ProblemDetail in org.springframework.web
Modifier and TypeMethodDescriptionErrorResponse.getBody()
Return the body for the response, formatted as an RFC 7807ProblemDetail
whosestatus
should match the response status.final ProblemDetail
ErrorResponseException.getBody()
Return the body for the response.HttpMediaTypeException.getBody()
HttpRequestMethodNotSupportedException.getBody()
default ProblemDetail
ErrorResponse.updateAndGetBody
(MessageSource messageSource, Locale locale) Resolve thedetailMessageCode
and thetitleCode
through the givenMessageSource
, and if found, update the "detail" and "title!" fields respectively.ModifierConstructorDescriptionErrorResponseException
(HttpStatusCode status, ProblemDetail body, Throwable cause) Constructor with a givenProblemDetail
instance, possibly a subclass ofProblemDetail
with extended fields.ErrorResponseException
(HttpStatusCode status, ProblemDetail body, Throwable cause, String messageDetailCode, Object[] messageDetailArguments) Constructor with a givenProblemDetail
, and aMessageSource
code and arguments to resolve the detail message with. -
Uses of ProblemDetail in org.springframework.web.bind
-
Uses of ProblemDetail in org.springframework.web.context.request.async
-
Uses of ProblemDetail in org.springframework.web.multipart.support
Modifier and TypeMethodDescriptionMissingServletRequestPartException.getBody()
Return the body for the response, formatted as an RFC 7807ProblemDetail
whosestatus
should match the response status. -
Uses of ProblemDetail in org.springframework.web.reactive.result.method.annotation
Modifier and TypeMethodDescriptionprotected ProblemDetail
ResponseEntityExceptionHandler.createProblemDetail
(Exception ex, HttpStatusCode status, String defaultDetail, String detailMessageCode, Object[] detailMessageArguments, ServerWebExchange exchange) Convenience method to create aProblemDetail
for any exception that doesn't implementErrorResponse
, also performing aMessageSource
lookup for the "detail" field. -
Uses of ProblemDetail in org.springframework.web.servlet
-
Uses of ProblemDetail in org.springframework.web.servlet.mvc.method.annotation
Modifier and TypeMethodDescriptionprotected ProblemDetail
ResponseEntityExceptionHandler.createProblemDetail
(Exception ex, HttpStatusCode status, String defaultDetail, String detailMessageCode, Object[] detailMessageArguments, WebRequest request) Convenience method to create aProblemDetail
for any exception that doesn't implementErrorResponse
, also performing aMessageSource
lookup for the "detail" field.