|
|
@@ -160,8 +160,6 @@ If you are using Maven, the changes look like this:
|
|
160
|
160
|
|
|
161
|
161
|
This change isn't about comparing Tomcat vs. Jetty. Instead, it demonstrates how Spring Boot reacts to what is on your classpath.
|
|
162
|
162
|
|
|
163
|
|
-Another example is [Uploading Files][gs-uploading-files]. In that guide, you can see how Spring Boot reacts to adding a `MultipartConfigElement` to your application context. Spring Boot automatically plugs that bean into the DispatcherServlet and adds some other beans needed to support file uploads.
|
|
164
|
|
-
|
|
165
|
163
|
As you can see below, the code is the same as before:
|
|
166
|
164
|
|
|
167
|
165
|
<@snippet path="src/main/java/hello/Application.java" prefix="complete"/>
|
|
|
@@ -232,7 +230,7 @@ There is little change from the previous output, except there is no longer a `to
|
|
232
|
230
|
|
|
233
|
231
|
Otherwise, everything is the same, as it should be. Most beans listed above provide Spring MVC's production-grade features. Simply swapping one part, the servlet container, shouldn't cause a system-wide ripple.
|
|
234
|
232
|
|
|
235
|
|
-Add consumer-grade services
|
|
|
233
|
+Add production-grade services
|
|
236
|
234
|
------------------------------
|
|
237
|
235
|
If you are building a web site for your business, you probably need to add some management services. Spring Boot provides several out of the box with its [actuator module][spring-boot-actuator], such as health, audits, beans, and more.
|
|
238
|
236
|
|