tag:blogger.com,1999:blog-6245476510271728435.post8203543590899836045..comments2023-09-05T14:55:50.003+02:00Comments on Padcom's blog: Grails gotcha - controllers with same name in different packagesMatthias Hryniszakhttp://www.blogger.com/profile/11432592442831476478noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-6245476510271728435.post-61922084369450506222011-04-01T18:10:00.198+02:002011-04-01T18:10:00.198+02:00Naturally you can specify the full path to view (a...Naturally you can specify the full path to view (as in with the "/" at the beginning) and that would solve the issue of where to find the view file to render.Matthias Hryniszakhttps://www.blogger.com/profile/11432592442831476478noreply@blogger.comtag:blogger.com,1999:blog-6245476510271728435.post-39190820213498910332011-04-01T18:08:54.897+02:002011-04-01T18:08:54.897+02:00This solution is not without a glitch. The problem...This solution is not without a glitch. The problem is that you need to manually call the render method to be able to spit out some results. That's bad, I know.<br />Another thing is that depending on which mapping kicked in (the default one or the one with long controller class name as controller name) the views folder will be different.<br />If the long one will be used the whole class name will have to be the folder name for the system to find the view.Matthias Hryniszakhttps://www.blogger.com/profile/11432592442831476478noreply@blogger.com