SimpleFormController

Determine whether the given request is a form change request. A form change request changes the appearance of the form and should always show the new form, without validation.

Gets called by suppressValidation(HttpServletRequest) and processFormSubmission(HttpServletRequest, HttpServletResponse, Object, BindException). Consequently, this single method determines to suppress validation and to show the form view in any case.

The default implementation delegates to isFormChangeRequest(javax.servlet.http.HttpServletRequest).

Called during form submission if isFormChangeRequest(javax.servlet.http.HttpServletRequest) returns true. Allows subclasses to implement custom logic to modify the command object to directly modify data in the form.

The default implementation delegates to onFormChange(HttpServletRequest, HttpServletResponse, Object, BindException).

Simpler onFormChange variant, called by the full variant onFormChange(HttpServletRequest, HttpServletResponse, Object, BindException).

The default implementation is empty.

Simpler onSubmit variant. Called by the default implementation of the onSubmit(HttpServletRequest, HttpServletResponse, Object, BindException) variant with all parameters.

The default implementation calls onSubmit(Object), using the returned ModelAndView if actually implemented in a subclass. Else, the default behavior will apply: rendering the success view with the command and Errors instance as model.

Subclasses can override this to provide custom submission handling that does not need request and response.

Call errors.getModel() to populate the ModelAndView model with the command and the Errors instance, under the specified command name, as expected by the "spring:bind" tag.

Simplest onSubmit variant. Called by the default implementation of the onSubmit(Object, BindException) variant.

This implementation calls doSubmitAction(Object) and returns null as ModelAndView, making the calling onSubmit method perform its default rendering of the success view.

Subclasses can override this to provide custom submission handling that just depends on the command object. It's preferable to use either onSubmit(Object, BindException) or doSubmitAction(Object), though: Use the former when you want to build your own ModelAndView; use the latter when you want to perform an action and forward to the successView.

Submit callback with all parameters. Called in case of submit without errors reported by the registered validator, or on every submit if no validator.

The default implementation delegates to onSubmit(Object, BindException). For simply performing a submit action and rendering the specified success view, consider implementing doSubmitAction(Object) rather than an onSubmit variant.

Subclasses can override this to provide custom submission handling like storing the object to the database. Implementations can also perform custom validation and call showForm to return to the form. Do not implement multiple onSubmit methods: In that case, just this method will be called by the controller.

Call errors.getModel() to populate the ModelAndView model with the command and the Errors instance, under the specified command name, as expected by the "spring:bind" tag.

This implementation calls showForm(HttpServletRequest, HttpServletResponse, BindException) in case of errors, and delegates to the full onSubmit(HttpServletRequest, HttpServletResponse, Object, BindException)'s variant else.

This can only be overridden to check for an action that should be executed without respect to binding errors, like a cancel action. To just handle successful submissions without binding errors, override one of the onSubmit methods or doSubmitAction(Object).

Create a reference data map for the given request and command, consisting of bean name/bean instance pairs as expected by ModelAndView.

The default implementation delegates to referenceData(HttpServletRequest). Subclasses can override this to set reference data used in the view.

Create a reference data map for the given request. Called by the referenceData(HttpServletRequest, Object, Errors) variant with all parameters.

The default implementation returns null. Subclasses can override this to set reference data used in the view.

This implementation shows the configured form view, delegating to the analogous showForm(HttpServletRequest, HttpServletResponse, BindException, Map) variant with a "controlModel" argument.

Can be called within onSubmit(HttpServletRequest, HttpServletResponse, Object, BindException) implementations, to redirect back to the form in case of custom validation errors (errors not determined by the validator).

Can be overridden in subclasses to show a custom view, writing directly to the response or preparing the response before rendering a view.

If calling showForm with a custom control model in subclasses, it's preferable to override the analogous showForm version with a controlModel argument (which will handle both standard form showing and custom form showing then).

This implementation shows the configured form view.

Can be called within onSubmit(HttpServletRequest, HttpServletResponse, Object, BindException) implementations, to redirect back to the form in case of custom validation errors (errors not determined by the validator).

Can be overridden in subclasses to show a custom view, writing directly to the response or preparing the response before rendering a view.

This implementation delegates to isFormChangeRequest(HttpServletRequest, Object): A form change request changes the appearance of the form and should not get validated but just show the new form.