From b3112379062cc75e2507070e9f6e621bbb23a6e0 Mon Sep 17 00:00:00 2001 From: Andy Wilkinson Date: Sun, 12 Nov 2017 10:46:37 +0000 Subject: [PATCH] Update docs to reflect change to default Filter dispatcher type Closes gh-10888 See gh-7467 --- .../src/main/asciidoc/howto.adoc | 19 ++----------------- 1 file changed, 2 insertions(+), 17 deletions(-) diff --git a/spring-boot-project/spring-boot-docs/src/main/asciidoc/howto.adoc b/spring-boot-project/spring-boot-docs/src/main/asciidoc/howto.adoc index c22f25b234..bc524093fe 100644 --- a/spring-boot-project/spring-boot-docs/src/main/asciidoc/howto.adoc +++ b/spring-boot-project/spring-boot-docs/src/main/asciidoc/howto.adoc @@ -595,23 +595,8 @@ addition to the underlying component. [NOTE] ==== -If no `dispatcherType` is specified on a filter registration, it matches -`FORWARD`,`INCLUDE`, and `REQUEST`. If async has been enabled, it also matches `ASYNC`. - -If you are migrating a filter that has no `dispatcher` element in `web.xml`, you -need to specify a `dispatcherType` yourself, as shown in the following example: - -[source,java,indent=0,subs="verbatim,quotes,attributes"] ----- - @Bean - public FilterRegistrationBean myFilterRegistration() { - FilterRegistrationBean registration = new FilterRegistrationBean(); - registration.setDispatcherTypes(DispatcherType.REQUEST); - .... - - return registration; - } ----- +If no `dispatcherType` is specified on a filter registration, `REQUEST` is used. This +aligns with the Servlet Specification's default dispatcher type. ====