Besides my work at Hippo I’m quite a fan of Play framework. My first introduction to Play framework was back in 2011 just around the time I was about to attend Devoxx. Because of this I attended a talk at Devoxx by James Ward about Deploying Java & Play Framework Apps to the Cloud. I’ve been following James on Twitter since that day because he was playing around with quite some interesting technologies. Recently I noticed James introduced an interesting project called WebJars.
A while back I was playing around on some pet project with Groovy. For those of you that are not familiar with Groovy: Groovy is a dynamic language for the Java Virtual Machine. In other words you can write Groovy (scripts) and keep writing without having to recompile / deploy. Groovy can integrate with any framework or library out there, so I tried it on Hippo CMS as well.
As you might know Hippo CMS uses Apache Jackrabbit as the core for it’s content repository. One of Jackrabbits features is ‘search’ and the execution of most queries are delegated to Apache Lucene. If you want to keep the queries as fast as possible you sometimes have to analyze how your repository is behaving with the content in your project.
Ever wondered what your application was doing? Why that specific page was so slow? I’ve asked myself this question numerous times and always had to change some log level or attach a profiler to get actual feedback on what was going on inside my application.