<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.dzone.com/~d/styles/itemcontent.css"?><rss xmlns:dz="http://www.developerzone.com/modules/dz/1.0" xmlns:media="http://search.yahoo.com/mrss/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0" xml:base="http://groovy.dzone.com/">
  <channel>
    <title>Groovy Zone - Everything for the Groovy &amp; Grails developer</title>
    <link>http://groovy.dzone.com/</link>
    <description />
    <language>en</language>
          <atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.dzone.com/zones/groovy" /><feedburner:info uri="zones/groovy" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item>
    <title> Spocklight: Writing Assertions for Arguments Mock Methods </title>
    <link>http://feeds.dzone.com/~r/zones/groovy/~3/J-c01v0_jEQ/spocklight-writing-assertions</link>
    <description>My colleague Arthur Arts has written a blog post Tasty Test Tip: Using ArgumentCaptor for generic collections with Mockito.
 This inspired me to do the same in Spock.
      Preview Text:&amp;nbsp;
    
            
                     In Spock we can  get a hold on the arguments that are passed to method call of a mock and we can write assertions to check the parameters for certain conditions.      ...&lt;img src="http://feeds.feedburner.com/~r/zones/groovy/~4/J-c01v0_jEQ" height="1" width="1"/&gt;</description>
     <comments>http://java.dzone.com/articles/spocklight-writing-assertions#comments</comments>
 <category domain="http://groovy.dzone.com/taxonomy/term/38">groovy</category>
 <category domain="http://groovy.dzone.com/category/tags/spock">Spock</category>
 <category domain="http://groovy.dzone.com/taxonomy/term/77">test</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://groovy.dzone.com/crss/node/140243</wfw:commentRss>
 <dz:submitDate>Tue, 21 May 2013 01:17:21 -0400</dz:submitDate>
 <dz:readCount>1541</dz:readCount>
 <dz:commentCount>0</dz:commentCount>
 <dz:thumbnail>http://cdn.dzone.com/sites/all/files/preview-images/May/spock_2.jpg</dz:thumbnail>
 <dz:submitter> <dz:username>mrhaki</dz:username>
 <dz:userimage>http://groovy.dzone.com/sites/all/files/avatars/picture-142080.jpg</dz:userimage>
</dz:submitter>
 <pubDate>Tue, 21 May 2013 05:17:21 +0000</pubDate>
 <dc:creator>mrhaki</dc:creator>
 <guid isPermaLink="false">140243 at http://groovy.dzone.com</guid>
  <feedburner:origLink>http://java.dzone.com/articles/spocklight-writing-assertions</feedburner:origLink></item>
  <item>
    <title>Gradle Goodness: Running a Single Test</title>
    <link>http://feeds.dzone.com/~r/zones/groovy/~3/3g2u7PMY1Dc/gradle-goodness-running-single</link>
    <description>We can run test code with Gradle using the&amp;nbsp;test&amp;nbsp;task that is added by the Java plugin. By default all tests found in the project are executed. If we want to run a single test we can use the Java system property&amp;nbsp;test.single&amp;nbsp;with the name of the test. Actually the pattern for the system property is&amp;nbsp;taskName.single. The&amp;nbsp;taskName&amp;nbsp;is the name of the task of...&lt;img src="http://feeds.feedburner.com/~r/zones/groovy/~4/3g2u7PMY1Dc" height="1" width="1"/&gt;</description>
     <comments>http://java.dzone.com/articles/gradle-goodness-running-single#comments</comments>
 <category domain="http://groovy.dzone.com/category/tags/gradle">Gradle</category>
 <category domain="http://groovy.dzone.com/category/tags/tests">tests</category>
 <category domain="http://groovy.dzone.com/category/content-form/tips-and-tricks">Tips and Tricks</category>
 <category domain="http://groovy.dzone.com/category/dzone-taxonomy/groovy">Groovy</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://groovy.dzone.com/crss/node/139697</wfw:commentRss>
 <dz:submitDate>Fri, 17 May 2013 00:04:40 -0400</dz:submitDate>
 <dz:readCount>2896</dz:readCount>
 <dz:commentCount>0</dz:commentCount>
 <dz:thumbnail>http://cdn.dzone.com/sites/all/files/preview-images/May/fixing.png</dz:thumbnail>
 <dz:submitter> <dz:username>mrhaki</dz:username>
 <dz:userimage>http://groovy.dzone.com/sites/all/files/avatars/picture-142080.jpg</dz:userimage>
</dz:submitter>
 <pubDate>Fri, 17 May 2013 04:04:40 +0000</pubDate>
 <dc:creator>mrhaki</dc:creator>
 <guid isPermaLink="false">139697 at http://groovy.dzone.com</guid>
  <feedburner:origLink>http://java.dzone.com/articles/gradle-goodness-running-single</feedburner:origLink></item>
  <item>
    <title>Gradle Goodness: Show More Information About Failed Tests</title>
    <link>http://feeds.dzone.com/~r/zones/groovy/~3/-9LS-M38vNU/gradle-goodness-show-more</link>
    <description>Running tests in Gradle is easy. Normally if one of the tests fails the build fails as well. But we don't see immediately in the command-line output why a test fails. We must first open the generated HTML test report. But there are other ways as well.

First we create the following sample Gradle build file:// File: build.gradle
      Preview Text:&amp;nbsp;
    
            
                   ...&lt;img src="http://feeds.feedburner.com/~r/zones/groovy/~4/-9LS-M38vNU" height="1" width="1"/&gt;</description>
     <comments>http://java.dzone.com/articles/gradle-goodness-show-more#comments</comments>
 <category domain="http://groovy.dzone.com/category/tags/gradle">Gradle</category>
 <category domain="http://groovy.dzone.com/category/content-form/tips-and-tricks">Tips and Tricks</category>
 <category domain="http://groovy.dzone.com/category/dzone-taxonomy/groovy">Groovy</category>
 <category domain="http://groovy.dzone.com/category/dzone-taxonomy/languages">Languages</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://groovy.dzone.com/crss/node/139605</wfw:commentRss>
 <dz:submitDate>Tue, 14 May 2013 10:28:16 -0400</dz:submitDate>
 <dz:readCount>3438</dz:readCount>
 <dz:commentCount>0</dz:commentCount>
 <dz:thumbnail>http://cdn.dzone.com/sites/all/files/preview-images/May/gradle.png</dz:thumbnail>
 <dz:submitter> <dz:username>mrhaki</dz:username>
 <dz:userimage>http://groovy.dzone.com/sites/all/files/avatars/picture-142080.jpg</dz:userimage>
</dz:submitter>
 <pubDate>Tue, 14 May 2013 14:28:16 +0000</pubDate>
 <dc:creator>mrhaki</dc:creator>
 <guid isPermaLink="false">139605 at http://groovy.dzone.com</guid>
  <feedburner:origLink>http://java.dzone.com/articles/gradle-goodness-show-more</feedburner:origLink></item>
  <item>
    <title>Grails 2.2.2 and 2.3 M1 Released!</title>
    <link>http://feeds.dzone.com/~r/zones/groovy/~3/7uT46Qo9q2Q/grails-222-and-23-m1-was</link>
    <description>The Grails team is extremely pleased to announce the releases of Grails 2.1.5 and 2.2.2 and 2.3 M1. The releases 2.1.5 and 2.2.2 include dozens of bug fixes and improvements, while the 2.3 M1 is the first milestone release leading up to 2.3 GA.The 2.3 M1 release includes numerous features and improvements. The most significant of which are:

      Preview Text:&amp;nbsp;
    
            
           ...&lt;img src="http://feeds.feedburner.com/~r/zones/groovy/~4/7uT46Qo9q2Q" height="1" width="1"/&gt;</description>
     <comments>http://groovy.dzone.com/articles/grails-222-and-23-m1-was#comments</comments>
 <category domain="http://groovy.dzone.com/category/tags/grails">grails</category>
 <category domain="http://groovy.dzone.com/taxonomy/term/38">groovy</category>
 <category domain="http://groovy.dzone.com/category/content-form/news">News</category>
 <category domain="http://groovy.dzone.com/category/tags/spring-source">spring source</category>
 <category domain="http://groovy.dzone.com/category/dzone-taxonomy/tools-methods/tips-and-tricks">Tips and Tricks</category>
 <category domain="http://groovy.dzone.com/category/tags/web">web</category>
 <category domain="http://groovy.dzone.com/category/dzone-taxonomy/tools-methods">Tools &amp; Methods</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://groovy.dzone.com/crss/node/139363</wfw:commentRss>
 <dz:submitDate>Sun, 12 May 2013 00:55:19 -0400</dz:submitDate>
 <dz:readCount>1476</dz:readCount>
 <dz:commentCount>1</dz:commentCount>
 <dz:thumbnail>http://cdn.dzone.com/sites/all/files/preview-images/May/grails-manual-insert-query.png</dz:thumbnail>
 <dz:submitter> <dz:username>keuller</dz:username>
 <dz:userimage>http://groovy.dzone.com/sites/all/files/avatars/picture-169787.jpg</dz:userimage>
</dz:submitter>
 <pubDate>Sun, 12 May 2013 04:55:19 +0000</pubDate>
 <dc:creator>keuller</dc:creator>
 <guid isPermaLink="false">139363 at http://groovy.dzone.com</guid>
  <feedburner:origLink>http://groovy.dzone.com/articles/grails-222-and-23-m1-was</feedburner:origLink></item>
  <item>
    <title>Java EE 7 Approved!</title>
    <link>http://feeds.dzone.com/~r/zones/groovy/~3/d9tCczwbnt8/java-ee-7-approved</link>
    <description>Java EE 7 is officially done as of this week.&amp;nbsp; Linda DeMichiel just announced on the Oracle blog that the Java EE 7 Platform JSR, as well as the more compact Web Profile JSR for this EE version, have both been approved by the Java Community Process.Here's the complete list of 14 JSRs and 9 MRs (maintenance releases):
JSRs:

      Preview Text:&amp;nbsp;
    
            
                    Java...&lt;img src="http://feeds.feedburner.com/~r/zones/groovy/~4/d9tCczwbnt8" height="1" width="1"/&gt;</description>
     <comments>http://java.dzone.com/articles/java-ee-7-approved#comments</comments>
 <category domain="http://groovy.dzone.com/category/dzone-taxonomy/java">Java</category>
 <category domain="http://groovy.dzone.com/category/tags/java7-0">Java 7</category>
 <category domain="http://groovy.dzone.com/category/tags/java-ee-7">Java EE 7</category>
 <category domain="http://groovy.dzone.com/category/content-form/news">News</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://groovy.dzone.com/crss/node/138373</wfw:commentRss>
 <dz:submitDate>Tue, 30 Apr 2013 15:58:32 -0400</dz:submitDate>
 <dz:readCount>17190</dz:readCount>
 <dz:commentCount>4</dz:commentCount>
 <dz:thumbnail>http://cdn.dzone.com/sites/all/files/preview-images/April/Java_HULK_DUKE.png</dz:thumbnail>
 <dz:submitter> <dz:username>mitchp</dz:username>
 <dz:userimage>http://groovy.dzone.com/sites/all/files/avatars/picture-478055.jpg</dz:userimage>
</dz:submitter>
 <pubDate>Tue, 30 Apr 2013 19:58:32 +0000</pubDate>
 <dc:creator>mitchp</dc:creator>
 <guid isPermaLink="false">138373 at http://groovy.dzone.com</guid>
  <feedburner:origLink>http://java.dzone.com/articles/java-ee-7-approved</feedburner:origLink></item>
  <item>
    <title>Apache Camel 2.11 Unleashed!</title>
    <link>http://feeds.dzone.com/~r/zones/groovy/~3/nZSu3yY89ow/apache-camel-211-unleashed</link>
    <description>Apache Camel 2.11 has been released
	


 This blog post is a summary of the most noticeable new features and improvements.
      Preview Text:&amp;nbsp;
    
            
                    This blog post is a summary of the most noticeable new features and improvements in Camel 2.11.  For example there is camel-cmis which allows to integrate with content management systems, such as...&lt;img src="http://feeds.feedburner.com/~r/zones/groovy/~4/nZSu3yY89ow" height="1" width="1"/&gt;</description>
     <comments>http://java.dzone.com/articles/apache-camel-211-unleashed#comments</comments>
 <category domain="http://groovy.dzone.com/category/dzone-taxonomy/open-source/apache">Apache</category>
 <category domain="http://groovy.dzone.com/category/tags/apache-camel">Apache Camel</category>
 <category domain="http://groovy.dzone.com/category/dzone-taxonomy/java">Java</category>
 <category domain="http://groovy.dzone.com/category/dzone-taxonomy/open-source">Open Source</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://groovy.dzone.com/crss/node/138191</wfw:commentRss>
 <dz:submitDate>Tue, 30 Apr 2013 01:35:10 -0400</dz:submitDate>
 <dz:readCount>5776</dz:readCount>
 <dz:commentCount>0</dz:commentCount>
 <dz:thumbnail>http://cdn.dzone.com/sites/all/files/preview-images/April/Camel_1.jpg</dz:thumbnail>
 <dz:submitter> <dz:username>davsclaus</dz:username>
 <dz:userimage>http://groovy.dzone.com/sites/all/files/avatars/picture-354055.jpg</dz:userimage>
</dz:submitter>
 <pubDate>Tue, 30 Apr 2013 05:35:10 +0000</pubDate>
 <dc:creator>davsclaus</dc:creator>
 <guid isPermaLink="false">138191 at http://groovy.dzone.com</guid>
  <feedburner:origLink>http://java.dzone.com/articles/apache-camel-211-unleashed</feedburner:origLink></item>
  <item>
    <title>Develop a MongoDB Application with ZK &amp; Grails</title>
    <link>http://feeds.dzone.com/~r/zones/groovy/~3/rJSUmcQPzAY/develop-mongodb-application-zk</link>
    <description>Introduction

In this article, I'll show you how to create a MongoDB application using the new version of ZKGrails,&amp;nbsp;ZKGrails 2.2.&amp;nbsp;This application has been developed by following Simon's&amp;nbsp;MongoMaps application&amp;nbsp;also on DZone. At the end of this article, you will find yourself be able to create a simple MongoDB application with ZK and Grails.
      Preview Text:&amp;nbsp;
    
      ...&lt;img src="http://feeds.feedburner.com/~r/zones/groovy/~4/rJSUmcQPzAY" height="1" width="1"/&gt;</description>
     <comments>http://architects.dzone.com/articles/develop-mongodb-application-zk#comments</comments>
 <category domain="http://groovy.dzone.com/category/tags/grails">grails</category>
 <category domain="http://groovy.dzone.com/category/tags/mongodb">MongoDB</category>
 <category domain="http://groovy.dzone.com/category/dzone-taxonomy/tools-methods/tips-and-tricks">Tips and Tricks</category>
 <category domain="http://groovy.dzone.com/category/content-form/tutorials">Tutorial</category>
 <category domain="http://groovy.dzone.com/category/tags/zk">ZK</category>
 <category domain="http://groovy.dzone.com/category/dzone-taxonomy/tools-methods">Tools &amp; Methods</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://groovy.dzone.com/crss/node/138095</wfw:commentRss>
 <dz:submitDate>Mon, 29 Apr 2013 00:40:29 -0400</dz:submitDate>
 <dz:readCount>4003</dz:readCount>
 <dz:commentCount>0</dz:commentCount>
 <dz:thumbnail>http://cdn.dzone.com/sites/all/files/preview-images/April/grails-logo_3.png</dz:thumbnail>
 <dz:submitter> <dz:username>Chanwit Kaewkasi</dz:username>
 <dz:userimage>http://groovy.dzone.com/sites/all/files/avatars/picture-396749.png</dz:userimage>
</dz:submitter>
 <pubDate>Mon, 29 Apr 2013 04:40:29 +0000</pubDate>
 <dc:creator>Chanwit Kaewkasi</dc:creator>
 <guid isPermaLink="false">138095 at http://groovy.dzone.com</guid>
  <feedburner:origLink>http://architects.dzone.com/articles/develop-mongodb-application-zk</feedburner:origLink></item>
  <item>
    <title>Broad-Stack Tests</title>
    <link>http://feeds.dzone.com/~r/zones/groovy/~3/d3VcqPjBYxw/broad-stack-tests</link>
    <description>A broad-stack test is a test that exercises most of the parts of a large application. It's often referred to as an end-to-end test or full-stack test. It lies in contrast to a ComponentTest, which only exercises a well-defined part of a system. 
      Preview Text:&amp;nbsp;
    
            
                    A broad-stack test is a test that exercises most of the parts of a large application....&lt;img src="http://feeds.feedburner.com/~r/zones/groovy/~4/d3VcqPjBYxw" height="1" width="1"/&gt;</description>
     <comments>http://agile.dzone.com/articles/broad-stack-tests#comments</comments>
 <category domain="http://groovy.dzone.com/category/content-form/tips-and-tricks">Tips and Tricks</category>
 <category domain="http://groovy.dzone.com/category/dzone-taxonomy/tools-methods/testing">Testing</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://groovy.dzone.com/crss/node/137731</wfw:commentRss>
 <dz:submitDate>Thu, 25 Apr 2013 02:05:10 -0400</dz:submitDate>
 <dz:readCount>7090</dz:readCount>
 <dz:commentCount>0</dz:commentCount>
 <dz:thumbnail>http://cdn.dzone.com/sites/all/files/preview-images/April/200px-Pancake-512.png</dz:thumbnail>
 <dz:submitter> <dz:username>martinfowler</dz:username>
 <dz:userimage>http://groovy.dzone.com/sites/all/files/avatars/picture-323432.jpg</dz:userimage>
</dz:submitter>
 <pubDate>Thu, 25 Apr 2013 06:05:10 +0000</pubDate>
 <dc:creator>martinfowler</dc:creator>
 <guid isPermaLink="false">137731 at http://groovy.dzone.com</guid>
  <feedburner:origLink>http://agile.dzone.com/articles/broad-stack-tests</feedburner:origLink></item>
  <item>
    <title>Algorithm of the Week: Fountain Codes (from "Damn Cool Algorithms")</title>
    <link>http://feeds.dzone.com/~r/zones/groovy/~3/V09WeDfUkqg/algorithm-week-fountain-codes</link>
    <description>That's right, it's time for another episode of the frustratingly infrequent Damn Cool Algorithms series! If you're not familiar with it, you might want to check out some of the previous posts.
      Preview Text:&amp;nbsp;
    
            
                    Today&amp;#039;s subject is Fountain Codes, otherwise known as &amp;quot;rateless codes&amp;quot;. A fountain code is a way to take some data - a file,...&lt;img src="http://feeds.feedburner.com/~r/zones/groovy/~4/V09WeDfUkqg" height="1" width="1"/&gt;</description>
     <comments>http://java.dzone.com/articles/algorithm-week-fountain-codes#comments</comments>
 <category domain="http://groovy.dzone.com/category/dzone-taxonomy/computer-science/algorithms">Algorithms</category>
 <category domain="http://groovy.dzone.com/category/content-form/tutorials">Tutorial</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://groovy.dzone.com/crss/node/136825</wfw:commentRss>
 <dz:submitDate>Tue, 16 Apr 2013 09:52:55 -0400</dz:submitDate>
 <dz:readCount>14670</dz:readCount>
 <dz:commentCount>0</dz:commentCount>
 <dz:thumbnail>http://cdn.dzone.com/sites/all/files/preview-images/April/nova.jpg</dz:thumbnail>
 <dz:submitter> <dz:username>damncoolalgorithms</dz:username>
 <dz:userimage>http://groovy.dzone.com/sites/all/files/avatars/picture-1132697.jpg</dz:userimage>
</dz:submitter>
 <pubDate>Tue, 16 Apr 2013 13:52:55 +0000</pubDate>
 <dc:creator>damncoolalgorithms</dc:creator>
 <guid isPermaLink="false">136825 at http://groovy.dzone.com</guid>
  <feedburner:origLink>http://java.dzone.com/articles/algorithm-week-fountain-codes</feedburner:origLink></item>
  <item>
    <title>Mocking Static Methods in Groovy </title>
    <link>http://feeds.dzone.com/~r/zones/groovy/~3/jZri4vIxHoQ/mocking-static-methods-groovy</link>
    <description>Using Groovy to test not only other Groovy classes but also Java classes
 is an increasing popular approach given frameworks like Spock which 
facilitate Test Driven and Behaviour Driven Development. 

A common problem when testing though is having to deal with legacy code 
and more often than not having to mock&amp;nbsp;static methods calls. When 
writing tests in Groovy, the approach to mocking...&lt;img src="http://feeds.feedburner.com/~r/zones/groovy/~4/jZri4vIxHoQ" height="1" width="1"/&gt;</description>
     <comments>http://java.dzone.com/articles/mocking-static-methods-groovy#comments</comments>
 <category domain="http://groovy.dzone.com/category/content-form/tips-and-tricks">Tips and Tricks</category>
 <category domain="http://groovy.dzone.com/category/dzone-taxonomy/groovy">Groovy</category>
 <category domain="http://groovy.dzone.com/category/dzone-taxonomy/languages">Languages</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://groovy.dzone.com/crss/node/135907</wfw:commentRss>
 <dz:submitDate>Mon, 15 Apr 2013 01:24:47 -0400</dz:submitDate>
 <dz:readCount>4674</dz:readCount>
 <dz:commentCount>0</dz:commentCount>
 <dz:thumbnail>http://cdn.dzone.com/sites/all/files/preview-images/April/groovy-logo-medium_3.png</dz:thumbnail>
 <dz:submitter> <dz:username>gdhjones</dz:username>
 <dz:userimage>http://groovy.dzone.com/sites/all/files/avatars/picture-389933.jpg</dz:userimage>
</dz:submitter>
 <pubDate>Mon, 15 Apr 2013 05:24:47 +0000</pubDate>
 <dc:creator>gdhjones</dc:creator>
 <guid isPermaLink="false">135907 at http://groovy.dzone.com</guid>
  <feedburner:origLink>http://java.dzone.com/articles/mocking-static-methods-groovy</feedburner:origLink></item>
  <item>
    <title>Links You Don't Want To Miss (4/12)</title>
    <link>http://feeds.dzone.com/~r/zones/groovy/~3/aXt4wUHPQz0/dzone-links-you-dont-want-miss-44</link>
    <description>Node.js vs. PHP vs. Go
 Some rough benchmarking to learn a little bit about each of these languages and how they perform.14 Lessons Learned after 5 Years of Professional ProgrammingA great blog post with nice concise snippets of knowledge from a programmer of 5 years.
      Preview Text:&amp;nbsp;
    
            
                    A node v. php v. go benchmarking session and some cool CSS and Mac...&lt;img src="http://feeds.feedburner.com/~r/zones/groovy/~4/aXt4wUHPQz0" height="1" width="1"/&gt;</description>
     <comments>http://java.dzone.com/articles/dzone-links-you-dont-want-miss-44#comments</comments>
 <category domain="http://groovy.dzone.com/category/dzone-taxonomy/web-design/css">CSS</category>
 <category domain="http://groovy.dzone.com/category/content-form/news">News</category>
 <category domain="http://groovy.dzone.com/category/tags/nodejs">Node.js</category>
 <category domain="http://groovy.dzone.com/category/dzone-taxonomy/languages/javascript">Javascript</category>
 <category domain="http://groovy.dzone.com/category/dzone-taxonomy/languages/php">PHP</category>
 <category domain="http://groovy.dzone.com/category/dzone-taxonomy/tools-methods/version-control">Version Control</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://groovy.dzone.com/crss/node/136427</wfw:commentRss>
 <dz:submitDate>Fri, 12 Apr 2013 00:25:10 -0400</dz:submitDate>
 <dz:readCount>4203</dz:readCount>
 <dz:commentCount>0</dz:commentCount>
 <dz:thumbnail>http://cdn.dzone.com/sites/all/files/preview-images/April/css.jpg</dz:thumbnail>
 <dz:submitter> <dz:username>mitchp</dz:username>
 <dz:userimage>http://groovy.dzone.com/sites/all/files/avatars/picture-478055.jpg</dz:userimage>
</dz:submitter>
 <pubDate>Fri, 12 Apr 2013 04:25:10 +0000</pubDate>
 <dc:creator>mitchp</dc:creator>
 <guid isPermaLink="false">136427 at http://groovy.dzone.com</guid>
  <feedburner:origLink>http://java.dzone.com/articles/dzone-links-you-dont-want-miss-44</feedburner:origLink></item>
  <item>
    <title>Execution of Groovy Scripts from Java - XmlSlurper and MarkupBuilder in Mapping Issues </title>
    <link>http://feeds.dzone.com/~r/zones/groovy/~3/NzMpjC2n82c/execution-groovy-scripts-java</link>
    <description>Problem with mappings

In our project we came across a really big problem related to mapping. 
Having two systems that initially were defined by the BA to be somehwat 
simillar we have chosen the simple XSLT (done through Altova Mapforce) 
of the input message to the output one.

Afterwards it turned out that the functions required to perform a 
mapping are becoming enormous. An example of such...&lt;img src="http://feeds.feedburner.com/~r/zones/groovy/~4/NzMpjC2n82c" height="1" width="1"/&gt;</description>
     <comments>http://java.dzone.com/articles/execution-groovy-scripts-java#comments</comments>
 <category domain="http://groovy.dzone.com/category/dzone-taxonomy/java">Java</category>
 <category domain="http://groovy.dzone.com/category/content-form/tips-and-tricks">Tips and Tricks</category>
 <category domain="http://groovy.dzone.com/category/dzone-taxonomy/groovy">Groovy</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://groovy.dzone.com/crss/node/135213</wfw:commentRss>
 <dz:submitDate>Thu, 11 Apr 2013 01:27:39 -0400</dz:submitDate>
 <dz:readCount>3688</dz:readCount>
 <dz:commentCount>0</dz:commentCount>
 <dz:thumbnail>http://cdn.dzone.com/sites/all/files/preview-images/April/groovy-logo-medium_2.png</dz:thumbnail>
 <dz:submitter> <dz:username>gregorin</dz:username>
 <dz:userimage>http://groovy.dzone.com/sites/all/files/avatars/picture-966553.jpg</dz:userimage>
</dz:submitter>
 <pubDate>Thu, 11 Apr 2013 05:27:39 +0000</pubDate>
 <dc:creator>gregorin</dc:creator>
 <guid isPermaLink="false">135213 at http://groovy.dzone.com</guid>
  <feedburner:origLink>http://java.dzone.com/articles/execution-groovy-scripts-java</feedburner:origLink></item>
  <item>
    <title>Grails Key Considerations on NFR</title>
    <link>http://feeds.dzone.com/~r/zones/groovy/~3/kumiKLnxBWk/grails-key-considerations-nfr</link>
    <description>&amp;nbsp;Grails is an Open
Source, full stack, web application framework for the JVM. It takes advantage
of the Groovy programming language and convention over configuration to provide
a productive and stream-lined development experience




      Preview Text:&amp;nbsp;
    
            
                    Grails builds on several well-established software frameworks, and combines their functionality...&lt;img src="http://feeds.feedburner.com/~r/zones/groovy/~4/kumiKLnxBWk" height="1" width="1"/&gt;</description>
     <comments>http://groovy.dzone.com/articles/grails-key-considerations-nfr#comments</comments>
 <category domain="http://groovy.dzone.com/category/tags/architecture">Architecture</category>
 <category domain="http://groovy.dzone.com/category/tags/grails">grails</category>
 <category domain="http://groovy.dzone.com/taxonomy/term/38">groovy</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://groovy.dzone.com/crss/node/135979</wfw:commentRss>
 <dz:submitDate>Tue, 09 Apr 2013 01:58:03 -0400</dz:submitDate>
 <dz:readCount>2492</dz:readCount>
 <dz:commentCount>0</dz:commentCount>
 <dz:thumbnail>http://cdn.dzone.com/sites/all/files/preview-images/April/Screen Shot 2013-04-03 at 3.00.50 PM_0.png</dz:thumbnail>
 <dz:submitter> <dz:username>nitins30</dz:username>
 <dz:userimage>http://groovy.dzone.com/sites/all/files/avatars/picture-807547.jpg</dz:userimage>
</dz:submitter>
 <pubDate>Tue, 09 Apr 2013 05:58:03 +0000</pubDate>
 <dc:creator>nitins30</dc:creator>
 <guid isPermaLink="false">135979 at http://groovy.dzone.com</guid>
  <feedburner:origLink>http://groovy.dzone.com/articles/grails-key-considerations-nfr</feedburner:origLink></item>
  <item>
    <title>Links You Don't Want To Miss (4/5)</title>
    <link>http://feeds.dzone.com/~r/zones/groovy/~3/FHNYYypWosQ/dzone-links-you-dont-want-miss-41</link>
    <description>Media Queries are a HackA thoughtful take on how CSS could achieve true modularity for responsive sites -- not through media queries, but element queries.
      Preview Text:&amp;nbsp;
    
            
                    Today: Programming is terrible, but what can you do about it? An interview with Alan Key, the new Facebook Home, and the story behind O&amp;#039;Reilly&amp;#039;s book cover animals.    ...&lt;img src="http://feeds.feedburner.com/~r/zones/groovy/~4/FHNYYypWosQ" height="1" width="1"/&gt;</description>
     <comments>http://java.dzone.com/articles/dzone-links-you-dont-want-miss-41#comments</comments>
 <category domain="http://groovy.dzone.com/category/tags/links-you-dont-want-miss">links you don't want to miss</category>
 <category domain="http://groovy.dzone.com/category/content-form/tips-and-tricks">Tips and Tricks</category>
 <category domain="http://groovy.dzone.com/category/dzone-taxonomy/industry/news">News</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://groovy.dzone.com/crss/node/135703</wfw:commentRss>
 <dz:submitDate>Fri, 05 Apr 2013 02:22:53 -0400</dz:submitDate>
 <dz:readCount>6337</dz:readCount>
 <dz:commentCount>0</dz:commentCount>
 <dz:thumbnail>http://cdn.dzone.com/sites/all/files/preview-images/April/Screen Shot 2013-04-04 at 5.40.36 PM.png</dz:thumbnail>
 <dz:submitter> <dz:username>acoin</dz:username>
 <dz:userimage>http://groovy.dzone.com/sites/all/files/avatars/picture-1059807.jpg</dz:userimage>
</dz:submitter>
 <pubDate>Fri, 05 Apr 2013 06:22:53 +0000</pubDate>
 <dc:creator>acoin</dc:creator>
 <guid isPermaLink="false">135703 at http://groovy.dzone.com</guid>
  <feedburner:origLink>http://java.dzone.com/articles/dzone-links-you-dont-want-miss-41</feedburner:origLink></item>
  <item>
    <title>Grails Best Practices</title>
    <link>http://feeds.dzone.com/~r/zones/groovy/~3/Shtp6-lzAVQ/grails-best-practices</link>
    <description>Grails is designed to
be an interactive agile based rapid development framework which advocates convention
not configuration. This
article explained the usage and best practices around the Grails.



Domain-driven design


Always
use domain-driven design:
First create your basic domain model classes, and then use scaffolding to get
them online. This will help you stay motivated and understand...&lt;img src="http://feeds.feedburner.com/~r/zones/groovy/~4/Shtp6-lzAVQ" height="1" width="1"/&gt;</description>
     <comments>http://groovy.dzone.com/articles/grails-best-practices#comments</comments>
 <category domain="http://groovy.dzone.com/category/tags/grail">Grail</category>
 <category domain="http://groovy.dzone.com/taxonomy/term/38">groovy</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://groovy.dzone.com/crss/node/135513</wfw:commentRss>
 <dz:submitDate>Thu, 04 Apr 2013 01:47:25 -0400</dz:submitDate>
 <dz:readCount>4683</dz:readCount>
 <dz:commentCount>0</dz:commentCount>
 <dz:thumbnail>http://cdn.dzone.com/sites/all/files/preview-images/April/Screen Shot 2013-04-03 at 3.00.50 PM.png</dz:thumbnail>
 <dz:submitter> <dz:username>nitins30</dz:username>
 <dz:userimage>http://groovy.dzone.com/sites/all/files/avatars/picture-807547.jpg</dz:userimage>
</dz:submitter>
 <pubDate>Thu, 04 Apr 2013 05:47:25 +0000</pubDate>
 <dc:creator>nitins30</dc:creator>
 <guid isPermaLink="false">135513 at http://groovy.dzone.com</guid>
  <feedburner:origLink>http://groovy.dzone.com/articles/grails-best-practices</feedburner:origLink></item>
  </channel>
</rss>
