It looks like you wrote a new message for when the uniqueness constraint is violated, but the error you were getting (
Property [{0}] of class [{1}] cannot be null) was not a uniqueness problem - it was a something-was-null problem. That error got associated with the default.null.message (as it should) instead of your user.username.unique message.
Maybe the User instance you created didn't set the password or the email?
Chris
2012/8/7 bhushan154 [via Grails]
<[hidden email]>
Forgot to press the Upload button after selecting the file :)
Attached.
messages.zip