<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="/stylesheets/rss.css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Out of my mind...: Category Grails</title>
    <link>http://blog.fredjean.net/articles/category/grails</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>Frederic Jean's Random Thoughts</description>
    <item>
      <title>Looking At Grails (And Liking It)</title>
      <description>&lt;p&gt;
A few months ago, I was introduced to the &lt;a href="http://www.grails.org/"&gt;Grails&lt;/a&gt; project while attending a Boulder JUG meeting. It was just after they released they 0.1 release. It was a little rough around the edges. At the times, I thought it was just another Java based Ruby on Rails wannabe. As a result, I just ran the basic install, went through the quick start tutorial and moved on to more interesting (to me) projects.
&lt;/p&gt;&lt;p&gt;
I have since changed my mind.
&lt;/p&gt;&lt;p&gt;
We use a lot of &lt;a href="http://groovy.codehaus.org/"&gt;Groovy&lt;/a&gt; at &lt;a href="http://www.openlogic.com/"&gt;OpenLogic&lt;/a&gt;. We use it in our infrastructure. We use it to build our content packages. I tend to use it whenever I would have to write more catch clauses than they are lines of code that could possibly throw these exceptions. It&amp;#8217;s a great dynamic language in its own right, and it integrates seamlessly with Java code. 
&lt;/p&gt;&lt;p&gt;
Now, Grails happens to be written in Groovy. It does borrow concepts from Ruby on Rails such as Convention over Configurations, (dynamic) code generation and scaffolding while leveraging the power of existing libraries and framework such as &lt;a href="http://www.springframework.org/"&gt;Spring&lt;/a&gt;, &lt;a href="http://www.hibernate.org/"&gt;Hibernate&lt;/a&gt; and &lt;a href="http://www.opensymphony.com/sitemesh/"&gt;Sitemesh&lt;/a&gt;. I&amp;#8217;m just starting with it, and I&amp;#8217;m still learning the different &amp;#8220;grailisms&amp;#8221; used to code the applications, but I like it so far.
&lt;/p&gt;&lt;p&gt;
I&amp;#8217;ll keep looking at it and evaluate it for future project. In the mean time, I&amp;#8217;m starting with a pet project. It is similar to a different project I did while I was still at Sun. As a result, I already have a pretty good idea how to proceed with the project. That will help a lot. 
&lt;/p&gt;</description>
      <pubDate>Wed, 02 Aug 2006 04:57:58 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:79384f71-4067-4c4e-b5ab-04d67b226ea8</guid>
      <author>fred@fredjean.net (Frederic Jean)</author>
      <link>http://blog.fredjean.net/articles/2006/08/02/looking-at-grails-and-liking-it</link>
      <category>Java</category>
      <category>Groovy</category>
      <category>Grails</category>
      <trackback:ping>http://blog.fredjean.net/articles/trackback/46</trackback:ping>
    </item>
  </channel>
</rss>
