diff --git a/1.3.x/multi/multi__spring_cloud_context_application_context_services.html b/1.3.x/multi/multi__spring_cloud_context_application_context_services.html
index c6f26670..b7a505d9 100644
--- a/1.3.x/multi/multi__spring_cloud_context_application_context_services.html
+++ b/1.3.x/multi/multi__spring_cloud_context_application_context_services.html
@@ -133,7 +133,9 @@ locate a property source specific to this Environmentspring.application.name, as is done in the default
Config Server property source locator).If you create a jar with this class in it and then add a
META-INF/spring.factories containing:
org.springframework.cloud.bootstrap.BootstrapConfiguration=sample.custom.CustomPropertySourceLocator
then the "customProperty" PropertySource will show up in any
-application that includes that jar on its classpath.
The application will listen for an EnvironmentChangeEvent and react
+application that includes that jar on its classpath.
1.7 Logging Configuration
If you are going to use Spring Boot to configure log settings than
+you should place this configuration in `bootstrap.[yml | properties]
+if you would like it to apply to all events.
The application will listen for an EnvironmentChangeEvent and react
to the change in a couple of standard ways (additional
ApplicationListeners can be added as @Beans by the user in the
normal way). When an EnvironmentChangeEvent is observed it will
@@ -158,7 +160,7 @@ dynamically. Re-binding @ConfigurationProperties do
another large class of use cases, where you need more control over the
refresh, and where you need a change to be atomic over the whole
ApplicationContext. To address those concerns we have
-@RefreshScope.
A Spring @Bean that is marked as @RefreshScope will get special
+@RefreshScope.
A Spring @Bean that is marked as @RefreshScope will get special
treatment when there is a configuration change. This addresses the
problem of stateful beans that only get their configuration injected
when they are initialized. For instance if a DataSource has open
@@ -179,7 +181,7 @@ mean that all the @Beans defined in that class are
cannot rely on them being updated when a refresh is initiated, unless
it is itself in @RefreshScope (in which it will be rebuilt on a
refresh and its dependencies re-injected, at which point they will be
-re-initialized from the refreshed @Configuration).
1.9 Encryption and Decryption
Spring Cloud has an Environment pre-processor for decrypting
+re-initialized from the refreshed @Configuration).
1.10 Encryption and Decryption
Spring Cloud has an Environment pre-processor for decrypting
property values locally. It follows the same rules as the Config
Server, and has the same external configuration via encrypt.*. Thus
you can use encrypted values in the form {cipher}* and as long as
@@ -188,5 +190,5 @@ application context gets the Environment. To use th
features in an application you need to include Spring Security RSA in
your classpath (Maven co-ordinates
"org.springframework.security:spring-security-rsa") and you also need
-the full strength JCE extensions in your JVM.
If you are getting an exception due to "Illegal key size" and you are using Sun’s JDK, you need to install the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files. See the following links for more information:
Extract files into JDK/jre/lib/security folder (whichever version of JRE/JDK x64/x86 you are using).
For a Spring Boot Actuator application there are some additional management endpoints:
- POST to
/env to update the Environment and rebind @ConfigurationProperties and log levels /refresh for re-loading the boot strap context and refreshing the @RefreshScope beans/restart for closing the ApplicationContext and restarting it (disabled by default)/pause and /resume for calling the Lifecycle methods (stop() and start() on the ApplicationContext)
![[Note]](images/note.png) | Note |
|---|
If you disable the /restart endpoint then the /pause and /resume endpoints
+the full strength JCE extensions in your JVM. If you are getting an exception due to "Illegal key size" and you are using Sun’s JDK, you need to install the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files. See the following links for more information: Extract files into JDK/jre/lib/security folder (whichever version of JRE/JDK x64/x86 you are using). For a Spring Boot Actuator application there are some additional management endpoints: - POST to
/env to update the Environment and rebind @ConfigurationProperties and log levels /refresh for re-loading the boot strap context and refreshing the @RefreshScope beans/restart for closing the ApplicationContext and restarting it (disabled by default)/pause and /resume for calling the Lifecycle methods (stop() and start() on the ApplicationContext)
| Note |
|---|
If you disable the /restart endpoint then the /pause and /resume endpoints
will also be disabled since they are just a special case of /restart. |
|