{"id":49,"date":"2009-05-26T10:04:48","date_gmt":"2009-05-26T04:34:48","guid":{"rendered":"http:\/\/www.tothenew.com\/blog\/?p=49"},"modified":"2010-06-09T15:52:38","modified_gmt":"2010-06-09T10:22:38","slug":"command-objects","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/command-objects\/","title":{"rendered":"Command Objects"},"content":{"rendered":"

What is a command object ?
\n<\/strong>
\n Command object is a non persistent class used for data-validation. The main advantage of using the Command objects is that we can validate those forms that do not map to the domain class.<\/p>\n

Where to define command object ?<\/strong><\/p>\n

You can define command classes in the grails-app\/controllers<\/em> directory or even in the same file as a controller; or you may also define it in grails-app\/src\/groovy.<\/em><\/p>\n

How to define command object ?
\n<\/strong>
\nIn one of my recent\u00a0 projects I did it like this :<\/p>\n

public class RegisterUserCommand {\r\n\r\n    String username\r\n    String password\r\n    String firstName\r\n    String lastName\r\n    String email\r\n    String age\r\n\r\n        static constraints={\r\n        username blank:false,size:30\r\n        password blank:false\r\n        cardNo creditCard:true\r\n        firstName matches\/[A-Za-z ]\/\r\n        lastName matches \/[A-Aa-z ]\/\r\n        email blank:false,email:true\r\n        age range:18..60\r\n    }\r\n\r\n}<\/pre>\n
How to define custom validators ?<\/strong><\/p>\n
Lets us assume we ‘ve one more field as verifyPassword <\/em>and we want to match it to the password field. We ‘ll use custom validator as :<\/p>\n
verifyPassword blank:false,validator:{val,obj ->\r\n        if(!(val==obj.password))\r\n        return ['field.match.message','Cofirm Password ','Password']\r\n}<\/pre>\n
Note :Here we ‘ve returned our own customized message instead of the default error message, along with the parameters.The default error message<\/em> is implicitly returned when we use default validations.<\/p>\n
How to use our command object now ?<\/strong><\/p>\n
When a request comes in, Grails will automatically create a new instance of the command object, bind the incoming request parameters to the properties of the instance, and pass it to you as the argument.
\nThus,you can create or modify your controller action as :<\/p>\n
def registerUser = { RegisterUserCommand cmd ->\r\n    if(!cmd.hasErrors()) {\r\n        \/\/ your code does something\r\n    }\r\n    else{\r\n            \/\/ your code does something\r\n    }\r\n}\r\n\r\n}<\/pre>\n
How do I display error messages on my gsp page ?
\n<\/strong>
\nTo do so you first need to pass the command object to your gsp page as :<\/p>\n
     render (view:'myErrorPage', model:[myCmd:cmd])<\/pre>\n
 Then in the  myErrorPage.gsp <\/em>you can use g:renderErrors  tag to display the errors(if any). But before displaying errors u need to make sure there are errors by  making use of g:hasErrors tag :<\/p>\n
\r\n\r\n          
\r\n            \r\n          <\/div>\r\n   <\/g:hasErrors>\r\n<\/pre>\n
But it shows default error messages.How can I define my own error messages ?
\n<\/strong>
\nTo do so you need to modify the \/grails-app\/i18n\/message.properties_<\/em> file by creating your own messages or replacing the default messages by custom messages :<\/p>\n
\r\nfield.blank.message={0} cannot be blank\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 #my message for blank fields\r\nfields.does.not.match.message={3} and {4} do not match\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 # my verifyPassword error message\r\nfield.number.notallowed.message={3} must have alphabets only\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 # u can guess this<\/pre>\n
I can’t follow the parameterized messages..can u please ellaborate.
\n<\/strong>
\nThe error message\u00a0 is defined as:<\/p>\n
default.doesnt.match.message=Property [{0}] of class [{1}] with value [{2}] does not match the required pattern [{3}]<\/pre>\n
[{0}] = property
\n[{1}] = class
\n[{2}] = value
\n[{3}] = constraint<\/p>\n
The above example is a default message provided in the message.properties  file.One can easily modify the message to suit to the requirement.
\n Or you choose to define your own message.eg., for the example given in the begining , the error message for the verifyPassword<\/em> validator can be defined as :<\/p>\n
fields.does.not.match.message={3} and {4} does not match<\/pre>\n
 So in the validator the parameters and the message are returned as :<\/p>\n
return ['field.match.message','Cofirm Password ','Password']<\/pre>\n
Hope you find this useful.
\nImran Mir
\nimran@intelligrape.com<\/p>\n","protected":false},"excerpt":{"rendered":"
What is a command object ? Command object is a non persistent class used for data-validation. The main advantage of using the Command objects is that we can validate those forms that do not map to the domain class. Where to define command object ? You can define command classes in the grails-app\/controllers directory or […]<\/p>\n","protected":false},"author":6,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":9},"categories":[7],"tags":[103,107,104],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/49"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=49"}],"version-history":[{"count":0,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/49\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=49"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=49"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=49"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}