Annotation Interface RequestPart
Supported method argument types include
MultipartFile in conjunction with
conjunction with Servlet multipart requests, or otherwise for any other method
argument, the content of the part is passed through an
taking into consideration the 'Content-Type' header of the request part. This is
analogous to what @
RequestBody does to resolve an argument based on the
content of a non-multipart regular request.
Note that @
RequestParam annotation can also be used to associate the part
of a "multipart/form-data" request with a method argument supporting the same method
argument types. The main difference is that when the method argument is not a String
@RequestParam relies on type
conversion via a registered
RequestPart relies on
taking into consideration the 'Content-Type' header of the request part.
RequestParam is likely to be used with name-value form fields while
RequestPart is likely to be used with parts containing more complex content
e.g. JSON, XML).
Optional Element Summary
nameThe name of the part in the
"multipart/form-data"request to bind to.
requiredboolean requiredWhether the part is required.
true, leading to an exception being thrown if the part is missing in the request. Switch this to
falseif you prefer a
nullvalue if the part is not present in the request.