<?xml version="1.0"?>
<!-- RSS generated by Radio UserLand v8.2.1 on Mon, 15 Jan 2007 13:10:07 GMT -->
<rss version="2.0">
	<channel>
		<title>David Black: Groovy</title>
		<link>http://radio.weblogs.com/0146416/categories/groovy/</link>
		<description>The Groovy scripting language</description>
		<copyright>Copyright 2007 David Black</copyright>
		<lastBuildDate>Mon, 15 Jan 2007 13:10:07 GMT</lastBuildDate>
		<docs>http://backend.userland.com/rss</docs>
		<generator>Radio UserLand v8.2.1</generator>
		<managingEditor>dblack@codecurl.org</managingEditor>
		<webMaster>dblack@codecurl.org</webMaster>
		<category domain="http://www.weblogs.com/rssUpdates/changes.xml">rssUpdates</category> 
		<skipHours>
			<hour>23</hour>
			<hour>0</hour>
			<hour>1</hour>
			<hour>2</hour>
			<hour>3</hour>
			<hour>4</hour>
			<hour>5</hour>
			<hour>6</hour>
			</skipHours>
		<cloud domain="radio.xmlstoragesystem.com" port="80" path="/RPC2" registerProcedure="xmlStorageSystem.rssPleaseNotify" protocol="xml-rpc"/>
		<ttl>60</ttl>
		<item>
			<title>Eclipse + Groovy = Monkey?</title>
			<description>Two of my favorite things have come together. &lt;a href=&quot;http://groovy.codehaus.org/Groovy+Monkey&quot;&gt;Groovy Monkey&lt;/a&gt; is a dynamic scripting tool for the Eclipse Platform that
enables you to automate tasks, explore the Eclipse API and engage in
rapid prototyping. I&apos;ve wanted something for ages that allows me to test stuff out and rapidly prototype tooling.&lt;br&gt;</description>
			<guid>http://radio.weblogs.com/0146416/categories/groovy/2007/01/15.html#a79</guid>
			<pubDate>Mon, 15 Jan 2007 13:10:07 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=146416&amp;amp;p=79&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0146416%2F2007%2F01%2F15.html%23a79</comments>
			</item>
		<item>
			<title>Groovy 1.0 is available</title>
			<description>Groovy 1.0 has been &lt;a href=&quot;http://docs.codehaus.org/display/GROOVY/2007/01/02/Groovy+1.0+is+there&quot;&gt;released&lt;/a&gt;!&lt;br&gt;</description>
			<guid>http://radio.weblogs.com/0146416/categories/groovy/2007/01/03.html#a73</guid>
			<pubDate>Wed, 03 Jan 2007 08:11:28 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=146416&amp;amp;p=73&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0146416%2F2007%2F01%2F03.html%23a73</comments>
			</item>
		<item>
			<title>James Gosling and Groovy</title>
			<description>According to &lt;a href=&quot;http://glaforge.free.fr/weblog/index.php?itemid=185&amp;amp;catid=2&quot;&gt;Guillame LaForge&lt;/a&gt;, who is the Groovy project lead, &lt;a href=&quot;http://blogs.sun.com/jag/&quot;&gt;James Gosling&lt;/a&gt; has been using Groovy in some projects at Sun, and &lt;span style=&quot;font-style: italic;&quot;&gt;he likes it very much&lt;/span&gt;. How cool is that?! I am really looking forward to the publication of the first &lt;a href=&quot;http://www.manning.com/koenig/&quot;&gt;Groovy book&lt;/a&gt;, and the release of the first Groovy JSR release candidate, and hopefully before too long the big 1.0 ...&lt;br&gt;</description>
			<guid>http://radio.weblogs.com/0146416/categories/groovy/2006/09/01.html#a54</guid>
			<pubDate>Fri, 01 Sep 2006 10:00:23 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=146416&amp;amp;p=54&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0146416%2F2006%2F09%2F01.html%23a54</comments>
			</item>
		<item>
			<title>Groovy testing in action</title>
			<link>http://groovy.codehaus.org/Unit+Testing</link>
			<description>One of Groovys key use cases is unit testing. Groovy has the potential to save us all a lot of time (and typing) and encourage us to write more test cases than we are now, just because its so quick to do powerful stuff. With the JSR work now quite advanced, and the first book, &lt;a href=&quot;http://www.manning.com/koenig/&quot;&gt;Groovy in Action&lt;/a&gt;, due out in November, its almost time to seriously consider ditching Java completely for unit testing. &lt;br&gt;&lt;br&gt;</description>
			<guid>http://radio.weblogs.com/0146416/categories/groovy/2006/04/09.html#a32</guid>
			<pubDate>Sun, 09 Apr 2006 20:44:07 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=146416&amp;amp;p=32&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0146416%2F2006%2F04%2F09.html%23a32</comments>
			</item>
		<item>
			<title>Agila &amp; Groovy</title>
			<link>http://wiki.apache.org/agila/</link>
			<description>The BPM engine in Apache Agila now supports &lt;a href=&quot;http://groovy.codehaus.org/&quot;&gt;Groovy&lt;/a&gt; nodes, which is really neat as you can use Groovy to develop custom tasks for your workflows. You get all the usual benefits of Groovy of course, and in particular you can use Groovy markup builders to generate the form/page for the task that the HTTPRenderer (returned by the TaskActivity) generates.&lt;br&gt;&lt;br&gt;In the process definition XML, the following syntax clues Agila into the fact that the node is a Groovy script:&lt;br&gt;&lt;br&gt;&amp;lt;node id=&quot;3&quot; type=&quot;activity&quot; class=&quot;groovy:node/ExampleGroovyTask.groovy&quot; display_name=&quot;Example Groovy Task&quot;&amp;gt;&lt;br&gt;&lt;node id=&quot;3&quot; type=&quot;activity&quot; class=&quot;groovy:node/ExampleGroovyTask.groovy&quot; display_name=&quot;Example Groovy Task&quot;&gt;&lt;br&gt;There is an example Groovy task at&lt;br&gt;&lt;br&gt;src/test-resources/node/ExampleGroovyTask.groovy&lt;br&gt;&lt;br&gt;under the bpm module that is both Task and Renderer etc. to get you started.&lt;br&gt;&lt;br&gt;Thanks to Chris Lim for taking a look at this contribution and commiting it so quickly.&lt;br&gt;&lt;br&gt;&lt;/node&gt;</description>
			<guid>http://radio.weblogs.com/0146416/categories/groovy/2005/08/16.html#a24</guid>
			<pubDate>Tue, 16 Aug 2005 15:11:40 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=146416&amp;amp;p=24&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0146416%2F2005%2F08%2F16.html%23a24</comments>
			</item>
		<item>
			<title>Groovy JSR</title>
			<description>Way to go &lt;a href=&quot;http://radio.weblogs.com/0112098/&quot;&gt;James&lt;/a&gt;, the Groovy JSR-241 has been approved. Only a matter of time before its offically Groovy. Yeah, baby, yeah.&lt;br&gt;&lt;br&gt;</description>
			<guid>http://radio.weblogs.com/0146416/categories/groovy/2004/04/06.html#a18</guid>
			<pubDate>Tue, 06 Apr 2004 12:31:23 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=146416&amp;amp;p=18&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0146416%2F2004%2F04%2F06.html%23a18</comments>
			</item>
		</channel>
	</rss>
