<?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: REST: Lean JSON and XML from the same code</title>
	<atom:link href="http://codemonkeyism.com/rest-lean-json-and-xml-from-the-same-code/feed/" rel="self" type="application/rss+xml" />
	<link>http://codemonkeyism.com/rest-lean-json-and-xml-from-the-same-code/</link>
	<description></description>
	<lastBuildDate>Mon, 15 Mar 2010 13:03:45 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: definition texas holdem world pokerr tournament</title>
		<link>http://codemonkeyism.com/rest-lean-json-and-xml-from-the-same-code/comment-page-1/#comment-161638</link>
		<dc:creator>definition texas holdem world pokerr tournament</dc:creator>
		<pubDate>Thu, 04 Sep 2008 20:41:38 +0000</pubDate>
		<guid isPermaLink="false">http://stephan.reposita.org/archives/2008/04/04/rest-lean-json-and-xml-from-the-same-code/#comment-161638</guid>
		<description>&lt;strong&gt;definition texas holdem world pokerr tournament...&lt;/strong&gt;

boasters frill pitiful....</description>
		<content:encoded><![CDATA[<p><strong>definition texas holdem world pokerr tournament&#8230;</strong></p>
<p>boasters frill pitiful&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: stephan</title>
		<link>http://codemonkeyism.com/rest-lean-json-and-xml-from-the-same-code/comment-page-1/#comment-86157</link>
		<dc:creator>stephan</dc:creator>
		<pubDate>Wed, 07 May 2008 16:36:00 +0000</pubDate>
		<guid isPermaLink="false">http://stephan.reposita.org/archives/2008/04/04/rest-lean-json-and-xml-from-the-same-code/#comment-86157</guid>
		<description>Hallo Octavian:

I know XStream and quite like it. The problem with XStream is that as written in the post, I need a Java object for each representation with attributes and annotations, just to create an JSON representation of an object (and there are different representations, especially for aggregated data views)</description>
		<content:encoded><![CDATA[<p>Hallo Octavian:</p>
<p>I know XStream and quite like it. The problem with XStream is that as written in the post, I need a Java object for each representation with attributes and annotations, just to create an JSON representation of an object (and there are different representations, especially for aggregated data views)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Octavian NITA</title>
		<link>http://codemonkeyism.com/rest-lean-json-and-xml-from-the-same-code/comment-page-1/#comment-86055</link>
		<dc:creator>Octavian NITA</dc:creator>
		<pubDate>Wed, 07 May 2008 10:49:32 +0000</pubDate>
		<guid isPermaLink="false">http://stephan.reposita.org/archives/2008/04/04/rest-lean-json-and-xml-from-the-same-code/#comment-86055</guid>
		<description>Hi Stephan!

How about XStream? It&#039;s a very nice library that supports both XML and JSON. You might want to take a look... http://xstream.codehaus.org/json-tutorial.html

Cheers!</description>
		<content:encoded><![CDATA[<p>Hi Stephan!</p>
<p>How about XStream? It&#8217;s a very nice library that supports both XML and JSON. You might want to take a look&#8230; <a href="http://xstream.codehaus.org/json-tutorial.html" rel="nofollow">http://xstream.codehaus.org/json-tutorial.html</a></p>
<p>Cheers!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: stephan</title>
		<link>http://codemonkeyism.com/rest-lean-json-and-xml-from-the-same-code/comment-page-1/#comment-69114</link>
		<dc:creator>stephan</dc:creator>
		<pubDate>Mon, 07 Apr 2008 05:21:38 +0000</pubDate>
		<guid isPermaLink="false">http://stephan.reposita.org/archives/2008/04/04/rest-lean-json-and-xml-from-the-same-code/#comment-69114</guid>
		<description>Hi James, well it does. But then I couldn&#039;t control the JSON output. There are several discussions on the net on how to increase performance - one is to pack and reduce JSON output to inly the necessary data. And I wanted to have different representations for an item or list. Finally most often for SOFEA applications you do not have an 1:1 mapping for JSON data and Java objects, especially for aggregated data. Creating JAXB objects just for that data seems stupid.</description>
		<content:encoded><![CDATA[<p>Hi James, well it does. But then I couldn&#8217;t control the JSON output. There are several discussions on the net on how to increase performance &#8211; one is to pack and reduce JSON output to inly the necessary data. And I wanted to have different representations for an item or list. Finally most often for SOFEA applications you do not have an 1:1 mapping for JSON data and Java objects, especially for aggregated data. Creating JAXB objects just for that data seems stupid.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Lorenzen</title>
		<link>http://codemonkeyism.com/rest-lean-json-and-xml-from-the-same-code/comment-page-1/#comment-68497</link>
		<dc:creator>James Lorenzen</dc:creator>
		<pubDate>Fri, 04 Apr 2008 14:47:49 +0000</pubDate>
		<guid isPermaLink="false">http://stephan.reposita.org/archives/2008/04/04/rest-lean-json-and-xml-from-the-same-code/#comment-68497</guid>
		<description>Stephan,
I thought Jersey automatically handled the return content type for you? For example if your REST Service method returned a jaxb POJO, then Jersey controlled what format to return it (json or xml) based on the produce MIME Type header; or something like that. I could have sworn I have seen something like that.</description>
		<content:encoded><![CDATA[<p>Stephan,<br />
I thought Jersey automatically handled the return content type for you? For example if your REST Service method returned a jaxb POJO, then Jersey controlled what format to return it (json or xml) based on the produce MIME Type header; or something like that. I could have sworn I have seen something like that.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
