Spring Framework

frameworkspringspring-framework

You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Tree: c0b4e368dc

3.0.x

3.1.x

3.2.x

4.0.x

4.1.x

4.2.x

4.3.x

5.0.x

5.1.x

5.2.x

5.3.x

6.0.x

6.1.x

6.2.x

7.0.x

dependabot/npm_and_yarn/framework-docs/fast-xml-parser-5.5.7

docs-build

gh-pages

main

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'c0b4e368dc'

${ noResults }

spring-framework/spring-test

History

Sam Brannen 37dc211f58 Support named dispatchers in MockServletContext ... Currently the getNamedDispatcher(String) method of MockServletContext always returns null. This poses a problem in certain testing scenarios since one would always expect at least a default Servlet to be present. This is specifically important for web application tests that involve the DefaultServletHttpRequestHandler which attempts to forward to the default Servlet after retrieving it by name. Furthermore, there is no way to register a named RequestDispatcher with the MockServletContext. This commit addresses these issues by introducing the following in MockServletContext. - a new defaultServletName property for configuring the name of the default Servlet, which defaults to "default" - named RequestDispatchers can be registered and unregistered - a MockRequestDispatcher is registered for the "default" Servlet automatically in the constructor - when the defaultServletName property is set to a new value the the current default RequestDispatcher is unregistered and replaced with a MockRequestDispatcher for the new defaultServletName Issue: SPR-9587		14 years ago
..
src	Support named dispatchers in MockServletContext	14 years ago
.springBeans	Rename modules {org.springframework.*=>spring-*}	14 years ago