<?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: Spring controller forwarding</title>
	<atom:link href="http://www.tamersalama.com/2005/03/02/spring-controller-forwarding/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.tamersalama.com/2005/03/02/spring-controller-forwarding/</link>
	<description>of Tamer Salama</description>
	<pubDate>Thu, 20 Nov 2008 08:33:44 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Simon</title>
		<link>http://www.tamersalama.com/2005/03/02/spring-controller-forwarding/#comment-307</link>
		<dc:creator>Simon</dc:creator>
		<pubDate>Fri, 14 Apr 2006 19:32:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.tamersalama.com/2005/03/02/spring-controller-forwarding/#comment-307</guid>
		<description>According to the API docs the RedirectView  redirects to a URL "exposing all model attributes as HTTP query parameters" (this was true even in Spring 1.1). Thus your third option would work by putting the desired request attributes as model attributes rather than as session ones. That's pretty close to what you are after (albeit requiring redirection), isn't it?</description>
		<content:encoded><![CDATA[<p>According to the API docs the RedirectView  redirects to a URL &#8220;exposing all model attributes as HTTP query parameters&#8221; (this was true even in Spring 1.1). Thus your third option would work by putting the desired request attributes as model attributes rather than as session ones. That&#8217;s pretty close to what you are after (albeit requiring redirection), isn&#8217;t it?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.623 seconds -->
