<?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: Problems with Jersey, REST, JSON and UTF-8 [Update2]</title>
	<atom:link href="http://www.codemonkeyism.com/archives/2008/03/24/problems-with-jersey-rest-json-and-utf-8-update2/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.codemonkeyism.com/archives/2008/03/24/problems-with-jersey-rest-json-and-utf-8-update2/</link>
	<description>Programming is hard</description>
	<pubDate>Sat, 22 Nov 2008 12:30:04 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: stephan</title>
		<link>http://www.codemonkeyism.com/archives/2008/03/24/problems-with-jersey-rest-json-and-utf-8-update2/#comment-67281</link>
		<dc:creator>stephan</dc:creator>
		<pubDate>Sat, 29 Mar 2008 11:35:51 +0000</pubDate>
		<guid isPermaLink="false">http://stephan.reposita.org/archives/2008/03/24/problems-with-jersey-rest-json-and-utf-8-update2/#comment-67281</guid>
		<description>Thanks, that would be great. I've got a reply from Paul, see the comments on the other, and I hope the issue is resolved with Jersey 0.7.</description>
		<content:encoded><![CDATA[<p>Thanks, that would be great. I&#8217;ve got a reply from Paul, see the comments on the other, and I hope the issue is resolved with Jersey 0.7.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Lorenzen</title>
		<link>http://www.codemonkeyism.com/archives/2008/03/24/problems-with-jersey-rest-json-and-utf-8-update2/#comment-67261</link>
		<dc:creator>James Lorenzen</dc:creator>
		<pubDate>Sat, 29 Mar 2008 05:52:52 +0000</pubDate>
		<guid isPermaLink="false">http://stephan.reposita.org/archives/2008/03/24/problems-with-jersey-rest-json-and-utf-8-update2/#comment-67261</guid>
		<description>Funny. my team is currently doing a lot with utf-8, with jersey, and extjs for javascript i8ln support.
I believe we got around some of the issues by setting the response content type to text/html.
I am going to forward them this blog and they should comment on their solutions.</description>
		<content:encoded><![CDATA[<p>Funny. my team is currently doing a lot with utf-8, with jersey, and extjs for javascript i8ln support.<br />
I believe we got around some of the issues by setting the response content type to text/html.<br />
I am going to forward them this blog and they should comment on their solutions.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
