• Share on Tumblr
  • Sharebar

This post is about my experience of upgrading Grails application from 1.3.4 to 2.2.2. Before I start listing down changes I had to do for upgrade I would like to mention that initially I tried upgrading it to 1.3.7, 1.3.9 without much success as it started throwing many Hibernate errors in different areas of application which fortunately I didn’t face while upgrading to 2.2.2.

As mentioned in Pledbrook blog http://pledbrook.github.io/grails-howtos/en/upgradeToGrails2.html I started of with deleting the target directory and then ran

grails upgrade –force

As the web.xml for Grails 2 has changed so re-ran install templates command to replace the old one with the new one. In my case there were no custom changes in web.xml otherwise you should backup the current web.xml and copy your custom changes to the new one.

grails install-templates

Updated jodaTime dependency to latest version, old one was throwing “no such method null safe” error.

joda-time-1.6.jar -> joda-time-2.2.jar
joda-time-hibernate-1.2.jar – > joda-time-hibernate-1.3.jar

Now its mandatory to add @Validatable annotation in command objects otherwise it throws compilation error.

Its not a good practice to have business logic in controller, service should be used but in my case there was a public method which I had to make private.

name and from attribute in g:select are mandatory now.

One of the most weird issue I came across was in some parts of application I was getting error java.lang.IllegalArgumentException: wrong number of arguments and the reason was I had an event hook in one of my domain class afterLoad() and when I changed it to onLoad() it got fixed.

There was some code in the constructor of service which I had to re-factor and move it to other place as that also caused issues.

Also re-factored code in-case a service injected in taglib had a cyclic dependency with other services.

Upgraded rendering plugin from rendering:0.3 to rendering:0.4.4 as it was throwing some plugin descriptor error.

Make sure you also update log configuration where you have defined grails packages as following have changed.

service -> services
controller -> controllers
tagLib -> taglib

As we are using logback instead of log4j so had to exclude plugin grails-plugin-log4j

inherits("global") {
excludes "slf4j-log4j12", "grails-plugin-log4j"

I hope this helps other planning to upgrade Grails to version 2.

Tagged with:

2 Responses to Upgrading Grails from 1.3.4 to 2.2.2

  1. Lokanath Reddy says:

    Thanks for your post, There were few this i would like toshare addition to you

    1. BeforeInsert didn’t work for me for the domains idgenerator:’assigned’. So we have to assign to them manually, so change yourcode accordingly.

    2. Make sure that you are configuring the tablePerHierarchysettings based on your requirement,

    3. In 2.x version in-memory database has been changed to”org.h2.Driver” from “org.hsqldb.jdbcDriver”

    4. You need to configure the plugins in BuildConfig.groovyinstead of using “grails install-pluing” since this commanddeprecated in 2.x version

    5. In 2.x change your actions syntax from closures to methods, leveraging methods instead ofClosure properties has some advantages:

    1. Memory efficient

    2. Allow use of stateless controllers (singleton scope)

    3. You can override actions from subclasses and call the overridden superclass method with super.actionName()

    4. Methodscan be intercepted with standard proxying mechanisms, something that iscomplicated to do with Closures since they’re fields.



Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>