SpringCloud/spring-cloud-commons
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Clarify functionality available through /refresh

Browse Source
This commit is contained in:
Ryan Baxter
2018-01-30 10:28:35 -05:00
committed by GitHub
parent 45ebbc593b
commit 13237ee38b
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/src/main/asciidoc/spring-cloud-commons.adoc
View File

@@ -269,9 +269,9 @@ 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.
NOTE: `@RefreshScope` works (technically) on an `@Configuration`
class, but it might lead to surprising behaviour: e.g. it does *not*
@@ -614,4 +614,4 @@ HTTP client and `OkHttpClientConnectionPoolFactory` for the OK HTTP client. You
your own implementation of these beans if you would like to customize how the HTTP clients are created
in downstream projects. You can also disable the creation of these beans by setting
`spring.cloud.httpclientfactories.apache.enabled` or `spring.cloud.httpclientfactories.ok.enabled` to
`false`.
`false`.