From f49d3518a815e8dfc3376a0704f2bee8b40fdfbd Mon Sep 17 00:00:00 2001 From: Phillip Webb Date: Tue, 9 Dec 2014 13:39:02 -0800 Subject: [PATCH] Javadoc SpringBootServletInitializer with @Ordered Fixes gh-2098 --- .../boot/context/web/SpringBootServletInitializer.java | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) 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 89812a95e4..4a48cae122 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 @@ -46,7 +46,10 @@ import org.springframework.web.context.WebApplicationContext; * To configure the application either override the * {@link #configure(SpringApplicationBuilder)} method (calling * {@link SpringApplicationBuilder#sources(Object...)}) or make the initializer itself a - * {@code @Configuration}. + * {@code @Configuration}. If you are using {@link SpringBootServletInitializer} in + * combination with other {@link WebApplicationInitializer WebApplicationInitializers} you + * might also want to add an {@code @Ordered} annotation to configure a specific startup + * order. *

* 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 then you won't need this at