You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since 3.1, RedirectView falls back to a ContextLoader.getCurrentWebApplicationContext() check to determine the ServletContext for building a RequestContext, which in turn gets used to retrieve the current RequestDataValueProcessor (if any). This doesn't seem to be the best possible arrangement, since the ServletContext is just used to retrieve the root WebApplicationContext... when we actually started with a current WebApplicationContext to begin with! Also, there is HttpServletRequest.getServletContext() since Servlet 3.0... even if there is probably no benefit in using that one here, it's generally preferable to a WebApplicationContext.getServletContext() lookup.
Uh oh!
There was an error while loading. Please reload this page.
Juergen Hoeller opened SPR-13346 and commented
Since 3.1,
RedirectView
falls back to aContextLoader.getCurrentWebApplicationContext()
check to determine theServletContext
for building aRequestContext
, which in turn gets used to retrieve the currentRequestDataValueProcessor
(if any). This doesn't seem to be the best possible arrangement, since theServletContext
is just used to retrieve the rootWebApplicationContext
... when we actually started with a currentWebApplicationContext
to begin with! Also, there isHttpServletRequest.getServletContext()
since Servlet 3.0... even if there is probably no benefit in using that one here, it's generally preferable to aWebApplicationContext.getServletContext()
lookup.Affects: 4.2 GA
Issue Links:
Referenced from: commits 4314da9
The text was updated successfully, but these errors were encountered: