See the DataBinder/WebDataBinder superclasses for customization options, which include specifying allowed/required fields, and registering custom property editors.
Used by Spring web MVC's BaseCommandController and MultiActionController.
Note that BaseCommandController and its subclasses allow for easy customization
of the binder instances that they use through overriding initBinder.
Can also be used for manual data binding in custom web controllers:
for example, in a plain Controller implementation or in a MultiActionController
handler method. Simply instantiate a ServletRequestDataBinder for each binding
process, and invoke bind with the current ServletRequest as argument:
MyBean myBean = new MyBean(); // apply binder to custom target object ServletRequestDataBinder binder = new ServletRequestDataBinder(myBean); // register custom editors, if desired binder.registerCustomEditor(...); // trigger actual binding of request parameters binder.bind(request); // optionally evaluate binding errors Errors errors = binder.getErrors(); ...
| Fields inherited from org.springframework.validationDataBinder |
|---|
| Fields inherited from org.springframework.web.bindWebDataBinder |
|---|
| Constructor Summary |
|---|
|
Create a new ServletRequestDataBinder instance, with default object name. |
|
Create a new ServletRequestDataBinder instance. |
| Method Summary | |
|---|---|
| void |
Bind the parameters of the given request to this binder's target, also binding multipart files in case of a multipart request. |
| protected void |
Check the multipart files contained in the given request, if any (in case of a multipart request). |
| void |
Treats errors as fatal. |
| boolean |
Return whether to bind empty MultipartFile parameters. |
| void |
Set whether to bind empty MultipartFile parameters. |
| Methods inherited from java.langObject |
|---|
| Methods inherited from org.springframework.beansPropertyEditorRegistry |
|---|
| Methods inherited from org.springframework.web.bindWebDataBinder |
|---|
This call can create field errors, representing basic binding errors like a required field (code "required"), or type mismatch between value and bean property (code "typeMismatch").
Multipart files are bound via their parameter name, just like normal HTTP parameters: i.e. "uploadedFile" to an "uploadedFile" bean property, invoking a "setUploadedFile" setter method.
The type of the target property for a multipart file can be MultipartFile, byte[], or String. The latter two receive the contents of the uploaded file; all metadata like original file name, content type, etc are lost in those cases.
Multipart files will only be added to the property values if they are not empty or if we're configured to bind empty multipart files too.
public
boolean
isBindEmptyMultipartFiles
(
)
public
void
setBindEmptyMultipartFiles
(
boolean
bindEmptyMultipartFiles
)
Turn this off if you want to keep an already bound MultipartFile when the user resubmits the form without choosing a different file. Else, the already bound MultipartFile will be replaced by an empty MultipartFile holder.
protected
void
