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
Couple of years ago I wasn't a big fan of unit testing. It was obvious to me that well prepared unit tests are crucial though. I didn't known why exactly crucial yet then. I just felt they are important. My disliking to write automation tests was mostly related to the effort necessary to prepare them. Also a spaghetti code was easily spotted in test sources.
