|
|
|
[
Permlink
| « Hide
]
Marc Palmer - 02/Nov/07 09:50 AM
This isolates the issue
Hmm I don't know what is up with this - any clues? See attached test project
Seems that constraints allow null values unless nullable:false is specified. Doing this fixes your test:
static constraints = { input(size:5..10, nullable:false) } It looks like there is an inconsistence between domain classes (where all properties are not nullable by default) and command objects, isn't it?
I think that a separate issue should be raised to apply nullable:false to command objects' properties by default. Thoughts? |
||||||||||||||||||||||||||||||||||||||||||||||||