As of Grails 2.1 command objects will no longer automatically be made validateable. If a command object class is not marked with @Validateable then the controller action will still accept the command object and will still do data binding but .validate() will not be invoked. A relevant compiler warning will be issued.
…m to be allowed on JDK 5
DefaultASTValidateableHelper was setting the return type of the validate method to be Boolean. The return type should be boolean.
…the use of generic types in transforms" This reverts commit dbbd267.
…of generic types in transforms
The constrainedProperties property that is added to validateable classes (like command object classes) is static. When the reloading agent reloads a class that property needs to be nulled out so that it will be re-initialized, in case the reload was initiated by changing constraints. This commit adds a statement to the validateable classes static initializer to null that property out. Grails runs the static initializer when classes are reloaded by the agent.
This reverts commit 8381b28.
…e via the grails.validateable.classes config property
…-plugin-validation sub project
…nsformation local transform
…er.currentWebApplicationContext and introduce some null safety which will help simplify some testing scenarios.
…ementing solution that does not involve turning @Validateables into Spring beans
… plugin in a jar file and then put that in your lib directory and have it appear as a regular plugin. View/template/layout resolution still not working though.
…mplemented yet, nor is view resolving. Still work to be done to get views, layouts and templates to resolve and to allow package-plugin to work with the binary format.
…the persistence tests