You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: spring-boot-project/spring-boot-actuator-autoconfigure/src/test/java/org/springframework/boot/actuate/autoconfigure/wavefront/WavefrontSenderConfigurationTests.java
Copy file name to clipboardexpand all lines: spring-boot-project/spring-boot-actuator/src/test/java/org/springframework/boot/actuate/mail/MailHealthIndicatorTests.java
Copy file name to clipboardexpand all lines: spring-boot-project/spring-boot-autoconfigure/src/main/resources/META-INF/spring/org.springframework.boot.autoconfigure.AutoConfiguration.imports
Copy file name to clipboardexpand all lines: spring-boot-project/spring-boot-autoconfigure/src/test/java/org/springframework/boot/autoconfigure/jackson/JacksonAutoConfigurationTests.java
Copy file name to clipboardexpand all lines: spring-boot-project/spring-boot-autoconfigure/src/test/java/org/springframework/boot/autoconfigure/web/client/RestTemplateAutoConfigurationTests.java
Copy file name to clipboardexpand all lines: spring-boot-project/spring-boot-docs/src/docs/asciidoc/howto/docker-compose.adoc
+1-1
Original file line number
Diff line number
Diff line change
@@ -35,4 +35,4 @@ With this Docker Compose file in place, the JDBC URL used is `jdbc:postgresql://
35
35
If you want to share services between multiple applications, create the `compose.yaml` file in one of the applications and then use the configuration property configprop:spring.docker.compose.file[] in the other applications to reference the `compose.yaml` file.
36
36
You should also set configprop:spring.docker.compose.lifecycle-management[] to `start-only`, as it defaults to `start-and-stop` and stopping one application would shut down the shared services for the other still running applications, too.
37
37
Setting it to `start-only` won't stop the shared services on application stop, but a caveat is that if you shut down all applications, the services stay running.
38
-
You can stop the services manually by running `docker compose stop` on the commandline in the directory which contains the `compose.yaml` file.
38
+
You can stop the services manually by running `docker compose stop` on the command line in the directory which contains the `compose.yaml` file.
Copy file name to clipboardexpand all lines: spring-boot-project/spring-boot-docs/src/docs/asciidoc/io/rest-client.adoc
+1-1
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ If you have Spring WebFlux on your classpath we recommend that you use `WebClien
12
12
The `WebClient` interface provides a functional style API and is fully reactive.
13
13
You can learn more about the `WebClient` in the dedicated {spring-framework-docs}/web/webflux-webclient.html[section in the Spring Framework docs].
14
14
15
-
TIP: If you are not writing a reactive Spring WebFlux application you can use the a <<io#io.rest-client.restclient,`RestClient`>> instead of a `WebClient`.
15
+
TIP: If you are not writing a reactive Spring WebFlux application you can use the <<io#io.rest-client.restclient,`RestClient`>> instead of a `WebClient`.
16
16
This provides a similar functional API, but is blocking rather than reactive.
17
17
18
18
Spring Boot creates and pre-configures a prototype `WebClient.Builder` bean for you.
@@ -291,7 +291,7 @@ The following example shows programmatically setting the port:
291
291
292
292
include::code:MyWebServerFactoryCustomizer[]
293
293
294
-
`JettyReactiveWebServerFactory`, `NettyReactiveWebServerFactory`, `TomcatReactiveWebServerFactory`, and `UndertowServletWebServerFactory` are dedicated variants of `ConfigurableReactiveWebServerFactory` that have additional customization setter methods for Jetty, Reactor Netty, Tomcat, and Undertow respectively.
294
+
`JettyReactiveWebServerFactory`, `NettyReactiveWebServerFactory`, `TomcatReactiveWebServerFactory`, and `UndertowReactiveWebServerFactory` are dedicated variants of `ConfigurableReactiveWebServerFactory` that have additional customization setter methods for Jetty, Reactor Netty, Tomcat, and Undertow respectively.
295
295
The following example shows how to customize `NettyReactiveWebServerFactory` that provides access to Reactor Netty-specific configuration options:
Copy file name to clipboardexpand all lines: spring-boot-project/spring-boot-docs/src/docs/asciidoc/web/servlet.adoc
+1-1
Original file line number
Diff line number
Diff line change
@@ -575,7 +575,7 @@ Usually, you would define the properties in your `application.properties` or `ap
575
575
576
576
Common server settings include:
577
577
578
-
* Network settings: Listen port for incoming HTTP requests (`server.port`), interface address to bind to `server.address`, and so on.
578
+
* Network settings: Listen port for incoming HTTP requests (`server.port`), interface address to bind to (`server.address`), and so on.
579
579
* Session settings: Whether the session is persistent (`server.servlet.session.persistent`), session timeout (`server.servlet.session.timeout`), location of session data (`server.servlet.session.store-dir`), and session-cookie configuration (`server.servlet.session.cookie.*`).
580
580
* Error management: Location of the error page (`server.error.path`) and so on.
Copy file name to clipboardexpand all lines: spring-boot-project/spring-boot-test-autoconfigure/src/test/java/org/springframework/boot/test/autoconfigure/web/servlet/SpringBootMockMvcBuilderCustomizerTests.java
Copy file name to clipboardexpand all lines: spring-boot-project/spring-boot-tools/spring-boot-loader/src/main/java/org/springframework/boot/loader/zip/ZipContent.java
+2-2
Original file line number
Diff line number
Diff line change
@@ -40,8 +40,8 @@
40
40
* contains. Unlike {@link java.util.zip.ZipFile}, this implementation can load content
41
41
* from a zip file nested inside another file as long as the entry is not compressed.
42
42
* <p>
43
-
* In order to reduce memory consumption, this implementation stores only the the hash of
44
-
* the entry names, the central directory offsets and the original positions. Entries are
43
+
* In order to reduce memory consumption, this implementation stores only the hash of the
44
+
* entry names, the central directory offsets and the original positions. Entries are
45
45
* stored internally in {@code hashCode} order so that a binary search can be used to
46
46
* quickly find an entry by name or determine if the zip file doesn't have a given entry.
0 commit comments