From 742e30b4757c0bd868118f18b49cccc22a3eeb1c Mon Sep 17 00:00:00 2001 From: buildmaster Date: Tue, 30 Jan 2018 15:29:27 +0000 Subject: [PATCH] Sync docs from master to gh-pages --- ...__spring_cloud_context_application_context_services.html | 6 +++--- single/spring-cloud-commons.html | 6 +++--- spring-cloud-commons.xml | 6 +++--- 3 files changed, 9 insertions(+), 9 deletions(-) diff --git a/multi/multi__spring_cloud_context_application_context_services.html b/multi/multi__spring_cloud_context_application_context_services.html index cdbb4381..7fde136f 100644 --- a/multi/multi__spring_cloud_context_application_context_services.html +++ b/multi/multi__spring_cloud_context_application_context_services.html @@ -169,9 +169,9 @@ used (i.e. when a method is called), and the scope acts as a cache of initialized values. To force a bean to re-initialize on the next method call you just need to invalidate its cache entry.

The RefreshScope is a bean in the context and it has a public method refreshAll() to refresh all beans in the scope by clearing the -target cache. There is also a refresh(String) method to refresh an -individual bean by name. This functionality is exposed in the -/refresh endpoint (over HTTP or JMX).

[Note]Note

@RefreshScope works (technically) on an @Configuration +target cache. This functionality is exposed in the +/refresh endpoint (over HTTP or JMX). There is also a refresh(String) method to refresh an +individual bean by name.

[Note]Note

@RefreshScope works (technically) on an @Configuration class, but it might lead to surprising behaviour: e.g. it does not mean that all the @Beans defined in that class are themselves @RefreshScope. Specifically, anything that depends on those beans diff --git a/single/spring-cloud-commons.html b/single/spring-cloud-commons.html index 40028341..3d734c20 100644 --- a/single/spring-cloud-commons.html +++ b/single/spring-cloud-commons.html @@ -169,9 +169,9 @@ used (i.e. when a method is called), and the scope acts as a cache of initialized values. To force a bean to re-initialize on the next method call you just need to invalidate its cache entry.

The RefreshScope is a bean in the context and it has a public method refreshAll() to refresh all beans in the scope by clearing the -target cache. There is also a refresh(String) method to refresh an -individual bean by name. This functionality is exposed in the -/refresh endpoint (over HTTP or JMX).

[Note]Note

@RefreshScope works (technically) on an @Configuration +target cache. This functionality is exposed in the +/refresh endpoint (over HTTP or JMX). There is also a refresh(String) method to refresh an +individual bean by name.

[Note]Note

@RefreshScope works (technically) on an @Configuration class, but it might lead to surprising behaviour: e.g. it does not mean that all the @Beans defined in that class are themselves @RefreshScope. Specifically, anything that depends on those beans diff --git a/spring-cloud-commons.xml b/spring-cloud-commons.xml index 3d23feff..14c1ed2b 100644 --- a/spring-cloud-commons.xml +++ b/spring-cloud-commons.xml @@ -269,9 +269,9 @@ initialized values. To force a bean to re-initialize on the next method call you just need to invalidate its cache entry. The RefreshScope is a bean in the context and it has a public method refreshAll() to refresh all beans in the scope by clearing the -target cache. There is also a refresh(String) method to refresh an -individual bean by name. This functionality is exposed in the -/refresh endpoint (over HTTP or JMX). +target cache. This functionality is exposed in the +/refresh endpoint (over HTTP or JMX). There is also a refresh(String) method to refresh an +individual bean by name. @RefreshScope works (technically) on an @Configuration class, but it might lead to surprising behaviour: e.g. it does not