<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for Technology Development, Engineering Management and Agile Processes</title>
	<atom:link href="http://johnragan.wordpress.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://johnragan.wordpress.com</link>
	<description>My experiences in developing, managing and applying Agile processes</description>
	<lastBuildDate>Wed, 11 Jan 2012 15:23:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>Comment on SOAP Messages &#8211; RPC vs. Document vs. Literal vs. Encoded vs. Wrapped vs. Unwrapped by sandocean</title>
		<link>http://johnragan.wordpress.com/2010/01/04/soap-messages-rpc-vs-document-vs-literal-vs-encoded-vs-wrapped-vs-unwrapped/#comment-170</link>
		<dc:creator><![CDATA[sandocean]]></dc:creator>
		<pubDate>Wed, 11 Jan 2012 15:23:40 +0000</pubDate>
		<guid isPermaLink="false">http://johnragan.org/?p=581#comment-170</guid>
		<description><![CDATA[Well not everything&#039;s completely correct here:

&quot;The rpc style is limited to very simple XSD types such as String and Integer&quot;. Well that&#039;s not a limitation of the rpc style. Using &quot;encoded&quot; allows you to specify the types of the XML directly. rpc just specifies that you use the operation name when invoking a web service.

&quot;However, the rpc style’s SOAP messages are easier to look at and understand.&quot;
I&#039;d say that&#039;s not true either. Encoded messages are harder to look at because of the type information. document/literal/wrapped and rpc literal style messages will probably look exactly the same. document/literal messages will even look simpler since you leave out the operation name.

Jax-WS RI (since Java 6 and above I think) uses document/literal/wrapped by default.]]></description>
		<content:encoded><![CDATA[<p>Well not everything&#8217;s completely correct here:</p>
<p>&#8220;The rpc style is limited to very simple XSD types such as String and Integer&#8221;. Well that&#8217;s not a limitation of the rpc style. Using &#8220;encoded&#8221; allows you to specify the types of the XML directly. rpc just specifies that you use the operation name when invoking a web service.</p>
<p>&#8220;However, the rpc style’s SOAP messages are easier to look at and understand.&#8221;<br />
I&#8217;d say that&#8217;s not true either. Encoded messages are harder to look at because of the type information. document/literal/wrapped and rpc literal style messages will probably look exactly the same. document/literal messages will even look simpler since you leave out the operation name.</p>
<p>Jax-WS RI (since Java 6 and above I think) uses document/literal/wrapped by default.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on User Stories Applied: For Agile Software Development by Mike Cohn by Revue du livre : User Story Applied de Mike Cohn &#171; Agile pour tous</title>
		<link>http://johnragan.wordpress.com/2010/05/27/user-stories-applied-for-agile-software-development-by-mike-cohn/#comment-168</link>
		<dc:creator><![CDATA[Revue du livre : User Story Applied de Mike Cohn &#171; Agile pour tous]]></dc:creator>
		<pubDate>Tue, 29 Nov 2011 00:41:06 +0000</pubDate>
		<guid isPermaLink="false">http://johnragan.org/?p=930#comment-168</guid>
		<description><![CDATA[[...] Article de Mike Cohn : http://johnragan.wordpress.com/2010/05/27/user-stories-applied-for-agile-software-development-by-mik... [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Article de Mike Cohn : <a href="http://johnragan.wordpress.com/2010/05/27/user-stories-applied-for-agile-software-development-by-mik.." rel="nofollow">http://johnragan.wordpress.com/2010/05/27/user-stories-applied-for-agile-software-development-by-mik..</a>. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Implementing the Java Messager Service (JMS) Request/Reply Pattern and Other Newbie Practice Runs by Swamy</title>
		<link>http://johnragan.wordpress.com/2010/01/11/jms-implementing-the-requestreply-pattern-and-other-newbie-practice-runs/#comment-158</link>
		<dc:creator><![CDATA[Swamy]]></dc:creator>
		<pubDate>Fri, 18 Feb 2011 13:04:08 +0000</pubDate>
		<guid isPermaLink="false">http://johnragan.org/?p=619#comment-158</guid>
		<description><![CDATA[Hi,

Was looking for the request/reply pattern in JMS. Found your article useful

A small change had to be made for the above code to work - the connection had to be started before the consumer receives the message.

I had a set up in which the producer and consumer were separate components within the ear file. 

Env: RAD 7.5.5]]></description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Was looking for the request/reply pattern in JMS. Found your article useful</p>
<p>A small change had to be made for the above code to work &#8211; the connection had to be started before the consumer receives the message.</p>
<p>I had a set up in which the producer and consumer were separate components within the ear file. </p>
<p>Env: RAD 7.5.5</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Clean Code and the 5S Principles by Ben</title>
		<link>http://johnragan.wordpress.com/2010/02/27/clean-code-and-the-5s-principles/#comment-156</link>
		<dc:creator><![CDATA[Ben]]></dc:creator>
		<pubDate>Tue, 11 Jan 2011 00:58:26 +0000</pubDate>
		<guid isPermaLink="false">http://johnragan.org/?p=813#comment-156</guid>
		<description><![CDATA[Should be &quot;seiketsu&quot; not &quot;seiketso&quot;. Thanks.]]></description>
		<content:encoded><![CDATA[<p>Should be &#8220;seiketsu&#8221; not &#8220;seiketso&#8221;. Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on ActiveMQ &#8211; Quick and Easy JMS Provider Installation and Workarounds by Alessandro</title>
		<link>http://johnragan.wordpress.com/2010/01/07/activemq-a-quick-and-easy-jms-provider-installation/#comment-130</link>
		<dc:creator><![CDATA[Alessandro]]></dc:creator>
		<pubDate>Thu, 17 Jun 2010 15:01:14 +0000</pubDate>
		<guid isPermaLink="false">http://johnragan.org/?p=602#comment-130</guid>
		<description><![CDATA[just... THANKS!!!]]></description>
		<content:encoded><![CDATA[<p>just&#8230; THANKS!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Choosing Clojure Over Scala by Jeoff Wilks</title>
		<link>http://johnragan.wordpress.com/2010/04/13/choosing-clojure-over-scala/#comment-113</link>
		<dc:creator><![CDATA[Jeoff Wilks]]></dc:creator>
		<pubDate>Thu, 22 Apr 2010 02:24:59 +0000</pubDate>
		<guid isPermaLink="false">http://johnragan.org/?p=888#comment-113</guid>
		<description><![CDATA[Very timely post. I was just messing with Scala a few days ago; there are a few nice things about it, but it also brings with it a lot of baggage, in my opinion. I haven&#039;t looked at Clojure yet, but hearing that it&#039;s more like Scheme than Common Lisp has got my attention.]]></description>
		<content:encoded><![CDATA[<p>Very timely post. I was just messing with Scala a few days ago; there are a few nice things about it, but it also brings with it a lot of baggage, in my opinion. I haven&#8217;t looked at Clojure yet, but hearing that it&#8217;s more like Scheme than Common Lisp has got my attention.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Choosing Clojure Over Scala by polypus74</title>
		<link>http://johnragan.wordpress.com/2010/04/13/choosing-clojure-over-scala/#comment-112</link>
		<dc:creator><![CDATA[polypus74]]></dc:creator>
		<pubDate>Wed, 21 Apr 2010 21:26:49 +0000</pubDate>
		<guid isPermaLink="false">http://johnragan.org/?p=888#comment-112</guid>
		<description><![CDATA[yeah, clojure is a lisp-1 but it has a macro system you usually find in lisp-2s (with improvements), and a more common lisp-like programming culture, and lacks call/cc. all of which make it, imo, something of a hybrid. i prefer it over all it&#039;s cousins though.]]></description>
		<content:encoded><![CDATA[<p>yeah, clojure is a lisp-1 but it has a macro system you usually find in lisp-2s (with improvements), and a more common lisp-like programming culture, and lacks call/cc. all of which make it, imo, something of a hybrid. i prefer it over all it&#8217;s cousins though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Choosing Clojure Over Scala by Michel S.</title>
		<link>http://johnragan.wordpress.com/2010/04/13/choosing-clojure-over-scala/#comment-111</link>
		<dc:creator><![CDATA[Michel S.]]></dc:creator>
		<pubDate>Wed, 21 Apr 2010 11:10:29 +0000</pubDate>
		<guid isPermaLink="false">http://johnragan.org/?p=888#comment-111</guid>
		<description><![CDATA[Fogus is too modest to mention this, but the second Clojure book everyone should read is his (and Chris Houser&#039;s) Joh of Clojure, still in pre-release.

Clojure is actually a Lisp (Lisp-1, like Scheme, unlike Common Lisp which is a Lisp-2). Though I guess nowadays Lisp is a convenient short-hand to mean Common Lisp.]]></description>
		<content:encoded><![CDATA[<p>Fogus is too modest to mention this, but the second Clojure book everyone should read is his (and Chris Houser&#8217;s) Joh of Clojure, still in pre-release.</p>
<p>Clojure is actually a Lisp (Lisp-1, like Scheme, unlike Common Lisp which is a Lisp-2). Though I guess nowadays Lisp is a convenient short-hand to mean Common Lisp.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Choosing Clojure Over Scala by John Ragan</title>
		<link>http://johnragan.wordpress.com/2010/04/13/choosing-clojure-over-scala/#comment-110</link>
		<dc:creator><![CDATA[John Ragan]]></dc:creator>
		<pubDate>Wed, 21 Apr 2010 00:27:41 +0000</pubDate>
		<guid isPermaLink="false">http://johnragan.org/?p=888#comment-110</guid>
		<description><![CDATA[Yep - I plan to be there!  :)]]></description>
		<content:encoded><![CDATA[<p>Yep &#8211; I plan to be there!  :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Choosing Clojure Over Scala by fogus</title>
		<link>http://johnragan.wordpress.com/2010/04/13/choosing-clojure-over-scala/#comment-109</link>
		<dc:creator><![CDATA[fogus]]></dc:creator>
		<pubDate>Tue, 20 Apr 2010 18:02:46 +0000</pubDate>
		<guid isPermaLink="false">http://johnragan.org/?p=888#comment-109</guid>
		<description><![CDATA[Have you been to the NoVA Clojure User Group?  We have another meeting this Thursday http://www.meetup.com/Cap-Clug

:f]]></description>
		<content:encoded><![CDATA[<p>Have you been to the NoVA Clojure User Group?  We have another meeting this Thursday <a href="http://www.meetup.com/Cap-Clug" rel="nofollow">http://www.meetup.com/Cap-Clug</a></p>
<p>:f</p>
]]></content:encoded>
	</item>
</channel>
</rss>

