Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

No—not through Spring Boot’s standard embedded Undertow setup. Spring Boot supports Undertow as an embedded servlet server, but its documentation states that “Undertow does not support JSPs.” For a conventional Spring Boot JSP application, use Tomcat or Jetty with WAR packaging instead.

Why JSPs fail when you switch Spring Boot to Undertow

Changing the embedded server changes the servlet container; it does not add a JSP engine. Spring Boot’s documented dependency switch replaces the Tomcat starter with spring-boot-starter-undertow, but Undertow does not provide JSP support in this arrangement. Adding Undertow-specific server configuration therefore does not make JSP views render.

Spring Boot’s reference guide explicitly says “Undertow does not support JSPs.” This is distinct from whether Undertow can serve a Spring MVC application: it can be used as the embedded servlet server, but not for the standard embedded JSP configuration.

Which Spring Boot setup should you choose?

Setup JSP compatibility Packaging Spring Boot support and trade-off
Embedded Undertow with spring-boot-starter-undertow Not supported for JSPs in Spring Boot’s documented setup Embedded-server applications can run without deploying a WAR Supported server choice, but not a JSP solution
Tomcat or Jetty with JSPs Supported by Spring Boot when using WAR packaging WAR; JSPs are not supported in an executable JAR Documented route for applications that need JSP views
Undertow with Jastow Potential custom integration path; not standard Spring Boot JSP support Not established as a standard Spring Boot packaging setup Requires custom integration beyond the normal starter configuration

Spring Boot’s JSP guidance covers the limitations of embedded servlet containers and says JSPs work with Tomcat or Jetty when packaged as a WAR. See the Spring Boot JSP limitations for the documented conditions.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

How to configure Undertow—and what that configuration changes

If your application does not need JSPs, the usual server switch is to remove the default Tomcat starter and add spring-boot-starter-undertow. Undertow can then be customized using Spring Boot’s UndertowServletWebServerFactory, WebServerFactoryCustomizer, and UndertowBuilderCustomizer APIs.

Those customizers configure the web server and its behavior; they do not provide JSP rendering. If the application still depends on JSP views, changing listeners or builder settings will not resolve that incompatibility. Spring Boot describes its embedded-server choices on its project page, which lists Tomcat, Jetty, and Undertow as embedded options.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

What about Jastow?

Undertow documentation mentions Jastow, a Jasper-derived project intended to provide JSP support without Tomcat dependencies. That is a separate integration, not the standard Spring Boot Undertow starter path. Treat it as custom integration work: its existence does not change Spring Boot’s documented statement that Undertow does not support JSPs in the standard embedded setup. See Undertow’s documentation for its mention of Jastow.

Practical decision

  • Keep JSPs: Use Tomcat or Jetty and package the application as a WAR.
  • Keep Undertow: Do not rely on JSPs in Spring Boot’s standard embedded setup; use a view technology supported by your chosen application architecture.
  • Need both Undertow and JSPs: Evaluate Jastow as a custom integration, understanding that it is outside Spring Boot’s documented embedded JSP support.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.