Using GORM standalone

Few days ago we decided to get rid of Apache iBatis in one of our projects. We couldn’t longer maintain large XML mapping and query descriptors with mix of Java, SQL and XML itself. But we also wanted to avoid switching to another ORM framework with lot of features and DAO layer requirement. We tried to implement some simple Spring JdbcTemplate-based ORM in Groovy, but it (strangely) started to look just like Hibernate… All that aliases in generated SQL’s, need to use javax.presistence annotations etc. The only simple existing solutions were Groovy’s DataSet (which is not working outside Groovy script) and GORM. Googling ‘GORM standalone’ show just few useful, but rather outdated, results. So I was forced to spend couple of hours to write desired 6 lines of code:

ExpandoMetaClass.enableGlobally()
        SessionFactory sessionFactory = ctx.getBean("sessionFactory")
        def grailsApp = new DefaultGrailsApplication([Customer.class] as Class[], null)
        grailsApp.initialise()
        GrailsHibernateUtil.configureHibernateDomainClasses(sessionFactory, grailsApp)
        HibernatePluginSupport.enhanceSessionFactory(sessionFactory, grailsApp, ctx)

And after annotating Customer class:

@Entity
@Table(name = "CUSTOMERS")
class Customer {
    String firstName
    String lastName
}

Now we are able to enjoy DAO-less code in pure Groovy:

Customer.findAll().each{ println it.firstName }         
        Customer.withCriteria { eq('lastName', 'Smith') }.each { Customer c -> println c.firstName }
        Customer.findByFirstNameAndLastName('John', 'Smith')

PS. For unknown reasons, these 6 lines work only with Grails 1.1.x

You May Also Like

New HTTP Logger Grails plugin

I've wrote a new Grails plugin - httplogger. It logs:

  • request information (url, headers, cookies, method, body),
  • grails dispatch information (controller, action, parameters),
  • response information (elapsed time and body).

It is mostly useful for logging your REST traffic. Full HTTP web pages can be huge to log and generally waste your space. I suggest to map all of your REST controllers with the same path in UrlMappings, e.g. /rest/ and configure this plugin with this path.

Here is some simple output just to give you a taste of it.

17:16:00,331 INFO  filters.LogRawRequestInfoFilter  - 17:16:00,340 INFO  filters.LogRawRequestInfoFilter  - 17:16:00,342 INFO  filters.LogGrailsUrlsInfoFilter  - 17:16:00,731 INFO  filters.LogOutputResponseFilter  - >> #1 returned 200, took 405 ms.
17:16:00,745 INFO filters.LogOutputResponseFilter - >> #1 responded with '{count:0}'
17:18:55,799 INFO  filters.LogRawRequestInfoFilter  - 17:18:55,799 INFO  filters.LogRawRequestInfoFilter  - 17:18:55,800 INFO  filters.LogRawRequestInfoFilter  - 17:18:55,801 INFO  filters.LogOutputResponseFilter  - >> #2 returned 404, took 3 ms.
17:18:55,802 INFO filters.LogOutputResponseFilter - >> #2 responded with ''

Official plugin information can be found on Grails plugins website here: http://grails.org/plugins/httplogger or you can browse code on github: TouK/grails-httplogger.