See the light - agile, industrial strength, rapid web application development made easy

(Quick Reference) # 10.6 Applying Validation to Other Classes - Reference Documentation Authors: Graeme Rocher, Peter Ledbrook, Marc Palmer, Jeff Brown, Luke Daley, Burt Beckwith, Lari Hotari Version: 2.3.8 ## 10.6 Applying Validation to Other Classes Domain classes and command objects support validation by default. Other classes may be made validateable by defining the static `constraints` property in the class (as described above) and then telling the framework about them. It is important that the application register the validateable classes with the framework. Simply defining the `constraints` property is not sufficient. #### The Validateable Annotation Classes which define the static `constraints` property and are annotated with @Validateable can be made validateable by the framework. Consider this example:

    // src/groovy/com/mycompany/myapp/User.groovy
    package com.mycompany.myappimport grails.validation.Validateable@Validateable
    class User {
        ...    static constraints = {
            login size: 5..15, blank: false, unique: true
            password size: 5..15, blank: false
            email email: true, blank: false
            age min: 18
        }
    }
#### Registering Validateable Classes If a class is not marked with `Validateable, it may still be made validateable by the framework. The steps required to do this are to define the static` constraints`property in the class (as described above) and then telling the framework about the class by assigning a value to the` grails.validateable.classes`property in` Config.groovy@:
    grails.validateable.classes = [com.mycompany.myapp.User, com.mycompany.dto.Account]
| Quick Reference (hide)