It’s obvious that the community is frustrated (from reading blogs and stack overflow questions) over that it’s quite hard to get a simple sample up and running even though I personally don’t share that feeling.
Sending data is not enough — we also need to make sure that the data users fill out in forms is in the correct format we need to process it successfully, and that it won't break our applications.
The In case you want to define a mapping from a custom object to a form field string and vice versa you need to register a new Formatter for this object.
The following example shows how the validation rules for the Most validators have default error messages that will be added to the model being validated when its attributes fail the validation.
For example, the required validator will add a message "Username cannot be blank." to a model when the Some validators may support additional error messages to more precisely describe different causes of validation failures.
In addition to providing instructions, validate user input to help users avoid mistakes.
HTML5 defines a range of built-in functionality to validate common types of input, such as email addresses and dates.
The entire code sample is available on Github, but you may also check out a live demo of the form.
Before you start with Play forms, read the documentation on the Play enhancer.
The code above is used to selectively show the zip code error message if the zip code field is both invalid and interacted with.
Another important piece is the form Control Name attribute - used to match the input field with the corresponding form control.
For example, the number validator supports too Big and too Small to describe the validation failure when the value being validated is too big and too small, respectively.
You may configure these error messages like configuring other properties of validators in a validation rule.