Reading the grails docs is like my habit, they always enhances your learning. Today I was going through the grails docs again and I found a very good way of showing some custom error messages. As I saw it I found the use case in one of my project that could be refactored by this approach<\/p>\n
There are use cases where we need to show some errors which are beyond your domain \/ command object constraints validators for these cases you can inject your custom error messages to the object take an example of updating the password. Any of the field is not domain related so we have to create a command object like <\/p>\n
[java]
\nclass UpdatePasswordCO {<\/p>\n
String password
\n String newPassword
\n String confirmNewPassword<\/p>\n
static constraints = {
\n password(nullable: false, blank: false)
\n newPassword(nullable: false, blank: false)
\n confirmNewPassword(nullable: false, blank: false, validator: {val, obj ->
\n if (obj.newPassword != val) {
\n "confirmPassword.mismatch.newPassword"
\n }
\n })
\n }
\n}
\n[\/java] <\/p>\n
Now you have to check whether the logged in user entered the correct password or not. So rather than putting the message in flash scope you can directly put this error to the command object it self<\/p>\n
[java]
\ndef updatePassword = {UpdatePasswordCO updatePasswordCO ->
\n if (updatePasswordCO.validate()) {
\n if (User.loggedInUser.validatePassword(updatePasswordCO.password)) {
\n flash.message = "Password updated successfully"
\n } else {
\n updatePasswordCO.errors.rejectValue("password", "password.mismatch.current.password")
\n }
\n }
\n if (updatePasswordCO.hasErrors()) {
\n render(view: ‘profile’, model: [updatePasswordCO: updatePasswordCO])
\n } else {
\n redirect(action: ‘profile’)
\n }
\n}
\n[\/java] <\/p>\n
So in above approach you have injected a new error on password field with a code. By doing this your hasErrors tag on gsp page will show your custom error as well. For more details you can refer Spring<\/a> Hope it helps Reading the grails docs is like my habit, they always enhances your learning. Today I was going through the grails docs again and I found a very good way of showing some custom error messages. As I saw it I found the use case in one of my project that could be refactored by this […]<\/p>\n","protected":false},"author":11,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":9,"footnotes":""},"categories":[7],"tags":[618,616,615,619,617],"class_list":["post-4055","post","type-post","status-publish","format-standard","hentry","category-grails","tag-add-custom-errors","tag-grails-command-object","tag-grails-object-validation","tag-grails-validation","tag-inject-errors-in-grails"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t
\n<\/p>\n
\nUday Pratap Singh<\/a>
\nuday@intelligrape.com<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"