Tag Archives: Groovy

Thanks to Payara we participated in the first edition of Devoxx Poland, on June, 22nd-24th, 2015 in Kraków, Poland. Last year we were on its ancestor — 33rd Degree (see our report of day 1, day 2 and day 3). What do we think about it? What … Continue reading →

On June, 9th — 11th, 2014 we were attending 33rd Degree conference in Cracow, Poland. In this series of posts, we’ll share our thoughts on the conference and particular talks. Besides, we’re going to point out the most interesting parts … Continue reading →

The last day was a bit shorter for us because we had to get back to home and also decided to do some networking instead of one talk, but still, we have some interesting takeaways from the talk we participated … Continue reading →

The list of transient property names in Grails domain-classes can get quite long in bigger setups. Also often multiple domain-classes share the same transient references so there are many places to keep synced when refactoring or extending. An easy alternative is to … Continue reading →

Very common task: you need to parse XML. When using groovy there is groovy.util.XmlSlurper for that. We know that HTML is just a special XML – but when you have to parse from online ressources you have to assume that it’s never … Continue reading →

Just had an old project that got both Grails Mail-plugin installed and also a custom EmailerService implemented. Problem was that both approaches are configuring a org.springframework.mail.javamail.JavaMailSenderImpl in two different ways. Grails Mail-Plugin was doing it via following Closure: [groovy title=”grails-app/conf/Config.groovy”] grails { mail { … Continue reading →

It can be very handy to use Grails console-plugin to investigate database-cache-related issues. For instance in a case where everything works as expected but still a certain value is not displayed on a view – the reason can be that an old … Continue reading →

When working with legacy-code it is often a good strategy to start increasing test-coverage. But writing tests without changing the legacy-code seems difficult to achieve in the most cases. Often it is enough to execute internal modules in isolation but … Continue reading →