mirror of
https://github.com/spring-projects/spring-boot.git
synced 2026-05-03 11:51:33 +01:00
Polish "Replace latin locutions in the documentation"
See gh-28141
This commit is contained in:
+1
-1
@@ -261,7 +261,7 @@ Here are some rules we follow internally to make sure descriptions are consisten
|
||||
* Do not start the description by "The" or "A".
|
||||
* For `boolean` types, start the description with "Whether" or "Enable".
|
||||
* For collection-based types, start the description with "Comma-separated list"
|
||||
* Use `java.time.Duration` rather than `long` and describe the default unit if it differs from milliseconds, for example "If a duration suffix is not specified, seconds will be used".
|
||||
* Use `java.time.Duration` rather than `long` and describe the default unit if it differs from milliseconds, such as "If a duration suffix is not specified, seconds will be used".
|
||||
* Do not provide the default value in the description unless it has to be determined at runtime.
|
||||
|
||||
Make sure to <<configuration-metadata#configuration-metadata.annotation-processor,trigger meta-data generation>> so that IDE assistance is available for your keys as well.
|
||||
|
||||
+3
-3
@@ -1048,7 +1048,7 @@ If you expose a `java.time.Duration` property, the following formats in applicat
|
||||
|
||||
* A regular `long` representation (using milliseconds as the default unit unless a `@DurationUnit` has been specified)
|
||||
* The standard ISO-8601 format {java-api}/java/time/Duration.html#parse-java.lang.CharSequence-[used by `java.time.Duration`]
|
||||
* A more readable format where the value and the unit are coupled (for example `10s` means 10 seconds)
|
||||
* A more readable format where the value and the unit are coupled (`10s` means 10 seconds)
|
||||
|
||||
Consider the following example:
|
||||
|
||||
@@ -1093,7 +1093,7 @@ The following formats can be used in application properties:
|
||||
|
||||
* An regular `int` representation (using days as the default unit unless a `@PeriodUnit` has been specified)
|
||||
* The standard ISO-8601 format {java-api}/java/time/Period.html#parse-java.lang.CharSequence-[used by `java.time.Period`]
|
||||
* A simpler format where the value and the unit pairs are coupled (for example `1y3d` means 1 year and 3 days)
|
||||
* A simpler format where the value and the unit pairs are coupled (`1y3d` means 1 year and 3 days)
|
||||
|
||||
The following units are supported with the simple format:
|
||||
|
||||
@@ -1112,7 +1112,7 @@ Spring Framework has a `DataSize` value type that expresses a size in bytes.
|
||||
If you expose a `DataSize` property, the following formats in application properties are available:
|
||||
|
||||
* A regular `long` representation (using bytes as the default unit unless a `@DataSizeUnit` has been specified)
|
||||
* A more readable format where the value and the unit are coupled (for example `10MB` means 10 megabytes)
|
||||
* A more readable format where the value and the unit are coupled (`10MB` means 10 megabytes)
|
||||
|
||||
Consider the following example:
|
||||
|
||||
|
||||
+1
-1
@@ -3,7 +3,7 @@
|
||||
Spring Boot supports localized messages so that your application can cater to users of different language preferences.
|
||||
By default, Spring Boot looks for the presence of a `messages` resource bundle at the root of the classpath.
|
||||
|
||||
NOTE: The auto-configuration applies when the default properties file for the configured resource bundle is available (that is `messages.properties` by default).
|
||||
NOTE: The auto-configuration applies when the default properties file for the configured resource bundle is available (`messages.properties` by default).
|
||||
If your resource bundle contains only language-specific properties files, you are required to add the default.
|
||||
If no properties file is found that matches any of the configured base names, there will be no auto-configured `MessageSource`.
|
||||
|
||||
|
||||
+1
-1
@@ -27,7 +27,7 @@ Those default settings can be fine-tuned using the `spring.task.execution` names
|
||||
This changes the thread pool to use a bounded queue so that when the queue is full (100 tasks), the thread pool increases to maximum 16 threads.
|
||||
Shrinking of the pool is more aggressive as threads are reclaimed when they are idle for 10 seconds (rather than 60 seconds by default).
|
||||
|
||||
A `ThreadPoolTaskScheduler` can also be auto-configured if need to be associated to scheduled task execution (for example `@EnableScheduling`).
|
||||
A `ThreadPoolTaskScheduler` can also be auto-configured if need to be associated to scheduled task execution (using `@EnableScheduling` for instance).
|
||||
The thread pool uses one thread by default and its settings can be fine-tuned using the `spring.task.scheduling` namespace, as shown in the following example:
|
||||
|
||||
[source,yaml,indent=0,subs="verbatim",configprops,configblocks]
|
||||
|
||||
@@ -36,7 +36,8 @@ See also the section on "`<<web#web.servlet.spring-mvc.error-handling, Error Han
|
||||
|
||||
[[howto.actuator.sanitize-sensitive-values]]
|
||||
=== Sanitize Sensitive Values
|
||||
Information returned by the `env` and `configprops` endpoints can be somewhat sensitive so keys matching certain patterns are sanitized by default (that is their values are replaced by `+******+`). Spring Boot uses sensible defaults for such keys: any key ending with the word "password", "secret", "key", "token", "vcap_services", "sun.java.command" is entirely sanitized.
|
||||
Information returned by the `env` and `configprops` endpoints can be somewhat sensitive so keys matching certain patterns are sanitized by default (that is their values are replaced by `+******+`).
|
||||
Spring Boot uses sensible defaults for such keys: any key ending with the word "password", "secret", "key", "token", "vcap_services", "sun.java.command" is entirely sanitized.
|
||||
Additionally, any key that holds the word `credentials` (configured as a regular expression, that is `+*credentials.*+`) as part of the key is also entirely sanitized.
|
||||
|
||||
Furthermore, Spring Boot sanitizes the sensitive portion of URI-like values for keys with one of the following endings:
|
||||
|
||||
@@ -106,6 +106,6 @@ See "`<<features#features.spring-application.fluent-builder-api>>`" in the '`Spr
|
||||
Not all Spring applications have to be web applications (or web services).
|
||||
If you want to execute some code in a `main` method but also bootstrap a Spring application to set up the infrastructure to use, you can use the `SpringApplication` features of Spring Boot.
|
||||
A `SpringApplication` changes its `ApplicationContext` class, depending on whether it thinks it needs a web application or not.
|
||||
The first thing you can do to help it is to leave server-related dependencies (for example servlet API) off the classpath.
|
||||
The first thing you can do to help it is to leave server-related dependencies (such as the servlet API) off the classpath.
|
||||
If you cannot do that (for example, you run two applications from the same code base) then you can explicitly call `setWebApplicationType(WebApplicationType.NONE)` on your `SpringApplication` instance or set the `applicationContextClass` property (through the Java API or with external properties).
|
||||
Application code that you want to run as your business logic can be implemented as a `CommandLineRunner` and dropped into the context as a `@Bean` definition.
|
||||
|
||||
Reference in New Issue
Block a user