From 9d9acc92e328159063b916083a2988b563869e04 Mon Sep 17 00:00:00 2001 From: Andy Wilkinson Date: Fri, 8 Jun 2018 15:43:39 +0100 Subject: [PATCH] Strengthen wording in JSP limitations regarding jar support Closes gh-13420 --- .../src/main/asciidoc/spring-boot-features.adoc | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc b/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc index 30e770b788c..2fc8fc2a8c9 100644 --- a/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc +++ b/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc @@ -2462,12 +2462,9 @@ source code documentation for details. When running a Spring Boot application that uses an embedded servlet container (and is packaged as an executable archive), there are some limitations in the JSP support. -* With Tomcat it should work if you use war packaging, i.e. an executable war will work, - and will also be deployable to a standard container (not limited to, but including - Tomcat). An executable jar will not work because of a hard coded file pattern in Tomcat. - -* With Jetty it should work if you use war packaging, i.e. an executable war will work, - and will also be deployable to any standard container. +* With Jetty and Tomcat it should work if you use war packaging. An executable war will + work when launched with `java -jar`, and will also be deployable to any standard + container. JSPs are not supported when using an executable jar. * Undertow does not support JSPs.