<?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"
	>
<channel>
	<title>Comments on: RESTEasy and Seam</title>
	<atom:link href="http://www.damnhandy.com/2008/07/02/resteasy-and-seam/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.damnhandy.com/2008/07/02/resteasy-and-seam/</link>
	<description>A blog about Java, REST, and other stuff.</description>
	<pubDate>Thu, 20 Nov 2008 12:09:38 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Jay Balunas</title>
		<link>http://www.damnhandy.com/2008/07/02/resteasy-and-seam/#comment-90162</link>
		<dc:creator>Jay Balunas</dc:creator>
		<pubDate>Wed, 02 Jul 2008 13:02:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.damnhandy.com/?p=164#comment-90162</guid>
		<description>This was exactly the type of discussion I was hoping would come out of my original post!!

I do think there are hurdles such as handling Seam injection, and seam component life cycle on a restful requests.  Obviously some type of filter would be needed, but how much of that fits in seam vs RESTeasy requires more baking.

I think your points around accessing an entity object graph as a single resource is very important.  When I was looking at RESTeasy one of my concerns was service class explosion.</description>
		<content:encoded><![CDATA[<p>This was exactly the type of discussion I was hoping would come out of my original post!!</p>
<p>I do think there are hurdles such as handling Seam injection, and seam component life cycle on a restful requests.  Obviously some type of filter would be needed, but how much of that fits in seam vs RESTeasy requires more baking.</p>
<p>I think your points around accessing an entity object graph as a single resource is very important.  When I was looking at RESTeasy one of my concerns was service class explosion.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
