<?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: Google App Engine + JAVA + Spring + REST + Mapping Exceptions to Errors for JSON</title>
	<atom:link href="http://www.wetfeetblog.com/google-app-engine-java-spring-rest-mapping-exceptions-to-errors-for-json/212/feed" rel="self" type="application/rss+xml" />
	<link>http://www.wetfeetblog.com/google-app-engine-java-spring-rest-mapping-exceptions-to-errors-for-json/212</link>
	<description></description>
	<lastBuildDate>Sun, 22 Jan 2012 04:28:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: anonym</title>
		<link>http://www.wetfeetblog.com/google-app-engine-java-spring-rest-mapping-exceptions-to-errors-for-json/212/comment-page-1#comment-1118</link>
		<dc:creator>anonym</dc:creator>
		<pubDate>Fri, 23 Dec 2011 15:55:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.wetfeetblog.com/?p=212#comment-1118</guid>
		<description>Thanks for pointing out how to use the exception resolver, but this aproach works if there is only JsonView (in your case it is named as MappingJacksonJsonView). Consider adding another media type (e.g. application/xml or text/plain), map for that content type a view. If there comes a request that accepts content type other than json, your exception resolver still will respond in a json format. This is beacause JsonExceptionResolver sets specifically JsonView.</description>
		<content:encoded><![CDATA[<p>Thanks for pointing out how to use the exception resolver, but this aproach works if there is only JsonView (in your case it is named as MappingJacksonJsonView). Consider adding another media type (e.g. application/xml or text/plain), map for that content type a view. If there comes a request that accepts content type other than json, your exception resolver still will respond in a json format. This is beacause JsonExceptionResolver sets specifically JsonView.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Spring 3 One Approach to Exception Handling for MVC when using JSON &#171; In the Folds</title>
		<link>http://www.wetfeetblog.com/google-app-engine-java-spring-rest-mapping-exceptions-to-errors-for-json/212/comment-page-1#comment-1117</link>
		<dc:creator>Spring 3 One Approach to Exception Handling for MVC when using JSON &#171; In the Folds</dc:creator>
		<pubDate>Thu, 17 Nov 2011 21:49:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.wetfeetblog.com/?p=212#comment-1117</guid>
		<description>[...] hope to discover and understand them at some point, but this was actually fairly simple. Thanks to Google App Engine + JAVA + Spring + REST + Mapping Exceptions to Errors for JSON for providing me with a solution. The entry at Wet Feet is very well written. I&#8217;m just [...]</description>
		<content:encoded><![CDATA[<p>[...] hope to discover and understand them at some point, but this was actually fairly simple. Thanks to Google App Engine + JAVA + Spring + REST + Mapping Exceptions to Errors for JSON for providing me with a solution. The entry at Wet Feet is very well written. I&#8217;m just [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

