tag:blogger.com,1999:blog-3237724005744642470.post8225583690499663948..comments2020-12-06T09:07:04.400+00:00Comments on Captain Debug's Blog: A Footnote on Accessing Request Parameters using Spring 3 MVCRoger Hugheshttp://www.blogger.com/profile/07042290171112551665[email protected]Blogger4125tag:blogger.com,1999:blog-3237724005744642470.post-30328269492264331392015-03-17T16:27:45.051+00:002015-03-17T16:27:45.051+00:00The automapping feature is core to the functionali...The automapping feature is core to the functionality of the grails framework, which is built around spring by teams at springsource/pivotal.Anonymoushttps://www.blogger.com/profile/00347301233200218540[email protected]tag:blogger.com,1999:blog-3237724005744642470.post-34226960396510781092013-10-13T22:26:44.333+01:002013-10-13T22:26:44.333+01:00From my experimentation if you leave off the @Requ...From my experimentation if you leave off the @RequestParam then it does not become a required parameter anymore. This of course can be bad if the method expects that value to not be null. Anonymous[email protected]tag:blogger.com,1999:blog-3237724005744642470.post-66379548250592928112013-10-12T09:03:10.023+01:002013-10-12T09:03:10.023+01:00But the second approach (automapping technique) ha...But the second approach (automapping technique) has much cleaner code....and if it is somewhere documented in spring, i am glad to see the automapping technique...<br /><br />I don&#39;t really like to use RequestParam annotation, as I find it redundant... But I also agree to the fact that you have specified here... that using undocumented features might be risky... :)<br /><br />Yogihttps://www.blogger.com/profile/15382350910254695035[email protected]tag:blogger.com,1999:blog-3237724005744642470.post-39935976932853790982012-09-30T11:30:50.930+01:002012-09-30T11:30:50.930+01:00I totally agree, the proposed solution may be more...I totally agree, the proposed solution may be more concise but it&#39;s a pain in the ass to read such a code. Instead reading a @RequestParam makes it obvious of what it is, and not some argument coming from an HandlerMethodArgumentResolver.<br /><br />CheersAnonymous[email protected]