<?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/"
		>
<channel>
	<title>Comments on: Conversational Pitfalls</title>
	<atom:link href="http://www.andygibson.net/blog/2009/11/17/conversational-pitfalls/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.andygibson.net/blog/article/conversational-pitfalls/</link>
	<description>Open Source Projects &#38; Technical Writings</description>
	<lastBuildDate>Wed, 18 Jan 2012 00:05:55 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Damon Chong</title>
		<link>http://www.andygibson.net/blog/article/conversational-pitfalls/comment-page-1/#comment-14422</link>
		<dc:creator>Damon Chong</dc:creator>
		<pubDate>Sat, 13 Mar 2010 07:01:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.andygibson.net/blog/?p=524#comment-14422</guid>
		<description>Thanks alot for this wonderful sharing! I have been struggling with conversations for a while even after having implemented 2 SEAM applications and now in the midst of another. Finally, someone says it like it is. Oftentimes, the official SEAM documentation just glosses over all these ugly stuff and harps on the great functionalities that SEAM offers to the world until...poor developers like me keep banging their heads on the wall....haha. Reading your article is like the revelation. Good job, man! Many thanks. ;-)</description>
		<content:encoded><![CDATA[<p>Thanks alot for this wonderful sharing! I have been struggling with conversations for a while even after having implemented 2 SEAM applications and now in the midst of another. Finally, someone says it like it is. Oftentimes, the official SEAM documentation just glosses over all these ugly stuff and harps on the great functionalities that SEAM offers to the world until&#8230;poor developers like me keep banging their heads on the wall&#8230;.haha. Reading your article is like the revelation. Good job, man! Many thanks. <img src='http://www.andygibson.net/blog/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nik Gardner</title>
		<link>http://www.andygibson.net/blog/article/conversational-pitfalls/comment-page-1/#comment-14276</link>
		<dc:creator>Nik Gardner</dc:creator>
		<pubDate>Mon, 14 Dec 2009 17:05:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.andygibson.net/blog/?p=524#comment-14276</guid>
		<description>Thanks Andy, great insight and a delightfully composed blog - I have to agree that you have to be careful using SMPC with nested conversations - its a real bugger and really gets under my skin! So from this day forward, I will use your line of thinking and no longer use nester conversations.
Many thanks.</description>
		<content:encoded><![CDATA[<p>Thanks Andy, great insight and a delightfully composed blog &#8211; I have to agree that you have to be careful using SMPC with nested conversations &#8211; its a real bugger and really gets under my skin! So from this day forward, I will use your line of thinking and no longer use nester conversations.<br />
Many thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Gibson</title>
		<link>http://www.andygibson.net/blog/article/conversational-pitfalls/comment-page-1/#comment-14272</link>
		<dc:creator>Andy Gibson</dc:creator>
		<pubDate>Thu, 19 Nov 2009 05:05:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.andygibson.net/blog/?p=524#comment-14272</guid>
		<description>Yes, I think I&#039;ve wrote about that issue before in one of my Seam documents, relating to the fact that multiple nested conversations use the same entity manager. However, I tend not to use nested conversations.</description>
		<content:encoded><![CDATA[<p>Yes, I think I&#8217;ve wrote about that issue before in one of my Seam documents, relating to the fact that multiple nested conversations use the same entity manager. However, I tend not to use nested conversations.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Huy Le</title>
		<link>http://www.andygibson.net/blog/article/conversational-pitfalls/comment-page-1/#comment-14271</link>
		<dc:creator>Huy Le</dc:creator>
		<pubDate>Wed, 18 Nov 2009 13:39:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.andygibson.net/blog/?p=524#comment-14271</guid>
		<description>Thanks for the helpful guidelines Andy :-)

We have use Seam at our company as well, and have found that even though conversations are quite nice conceptually, using it incorrectly can get you into a bit of trouble. In addition, we have found you have to be quite careful using SMPC with nested conversations, since even though the conversation is nested, the PC is not, so you may end up persisting things which you didn&#039;t intend to persist.</description>
		<content:encoded><![CDATA[<p>Thanks for the helpful guidelines Andy <img src='http://www.andygibson.net/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>We have use Seam at our company as well, and have found that even though conversations are quite nice conceptually, using it incorrectly can get you into a bit of trouble. In addition, we have found you have to be quite careful using SMPC with nested conversations, since even though the conversation is nested, the PC is not, so you may end up persisting things which you didn&#8217;t intend to persist.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

