<para>If you use <classname>RedirectView</classname> and the view is
<para>If you use <classname>RedirectView</classname> and the view is
created by the controller itself, it is recommended that you configure
created by the controller itself, it is recommended that you configure
the redirect URL to be injected into the controller so that it is not
the redirect URL to be injected into the controller so that it is not
baked into the controller but configured in the context along with the
baked into the controller but configured in the context along with the
view names. <!--I revised sentence because it sounds like something you need to do. Also reworded next heading to say what it's about. If not correct,--><!--reword.-->The
view names. The next section discusses this process.</para>
next section discusses this process.</para>
</section>
</section>
<sectionid="mvc-redirecting-redirect-prefix">
<sectionid="mvc-redirecting-redirect-prefix">
@ -2194,13 +2207,10 @@ public class TimeBasedAccessInterceptor extends HandlerInterceptorAdapter {
<para>The net effect is the same as if the controller had returned a
<para>The net effect is the same as if the controller had returned a
<classname>RedirectView</classname>, but now the controller itself can
<classname>RedirectView</classname>, but now the controller itself can
simply operate in terms of logical view names. A logical view name
simply operate in terms of logical view names. A logical view name
such as <literal>redirect:/my/response/controller.html</literal> will
such as <literal>redirect:/myapp/some/resource</literal> will
redirect relative to the current servlet context, while a name such as
redirect relative to the current servlet context, while a name such as