From 0ccbde9c9006046ea132f1b6a480348b1ea8d21f Mon Sep 17 00:00:00 2001 From: Dave Syer Date: Wed, 4 Jun 2014 10:29:11 +0100 Subject: [PATCH] Fix docs in ServletInitializer --- .../boot/context/web/SpringBootServletInitializer.java | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/spring-boot/src/main/java/org/springframework/boot/context/web/SpringBootServletInitializer.java b/spring-boot/src/main/java/org/springframework/boot/context/web/SpringBootServletInitializer.java index abbe9b22197..d7810542590 100644 --- a/spring-boot/src/main/java/org/springframework/boot/context/web/SpringBootServletInitializer.java +++ b/spring-boot/src/main/java/org/springframework/boot/context/web/SpringBootServletInitializer.java @@ -31,10 +31,10 @@ import org.springframework.web.context.ContextLoaderListener; import org.springframework.web.context.WebApplicationContext; /** - * A handy opinionated {@link WebApplicationInitializer} for applications that only have - * one Spring servlet, and no more than a single filter (which itself is only enabled when - * Spring Security is detected). If your application is more complicated consider using - * one of the other WebApplicationInitializers. + * A handy opinionated {@link WebApplicationInitializer} for applications that starts a + * Spring Boot application and lets it bind to the servlet and filter mappings. If your + * application is more complicated consider using one of the other + * WebApplicationInitializers. *

* Note that a WebApplicationInitializer is only needed if you are building a war file and * deploying it. If you prefer to run an embedded container (we do) then you won't need