Basically it turns the form fields into a command for the controller to process. The validator confirms that the command is valid. The trick is this: if the command isn't valid, then it gets used as the form backing object again. This gives you persistence between form invocations so the user doesn't simply get a blank form again.
A different kind of form that edits or creates a new object (like a user registration or edit form) would just use the business object that it's creating/editing. The Spring tutorial example is a bit wierd in the respect that they've chosen to demonstrate a true command as opposed to the Create/Update sort of thing you see more often.