From 6dc731fcd2d0cc0e67a8741188f8aa6b329bb564 Mon Sep 17 00:00:00 2001 From: buildmaster Date: Wed, 15 Jan 2020 15:19:59 +0000 Subject: [PATCH] Sync docs from master to gh-pages --- reference/html/index.html | 20 +++++++++++++++++++ .../html/spring-cloud-circuitbreaker.html | 20 +++++++++++++++++++ reference/html/spring-cloud-commons.html | 20 +++++++++++++++++++ 3 files changed, 60 insertions(+) diff --git a/reference/html/index.html b/reference/html/index.html index e3c5f136..b03c4292 100644 --- a/reference/html/index.html +++ b/reference/html/index.html @@ -1810,6 +1810,26 @@ the following documentation:

+
+

Some CircuitBreaker implementations such as Resilience4JCircuitBreaker call customize method every time CircuitBreaker#run is called. +It can be inefficient. In that case, you can use CircuitBreaker#once method. It is useful where calling customize many times doesn’t make sense, +for example, in case of consuming Resilience4j’s events.

+
+
+

The following example shows the way for each io.github.resilience4j.circuitbreaker.CircuitBreaker to consume events.

+
+
+
+
+
+
Customizer.once(circuitBreaker -> {
+  circuitBreaker.getEventPublisher()
+    .onStateTransition(event -> log.info("{}: {}", event.getCircuitBreakerName(), event.getStateTransition()));
+}, CircuitBreaker::getName)
+
+
+
+
diff --git a/reference/html/spring-cloud-circuitbreaker.html b/reference/html/spring-cloud-circuitbreaker.html index 9c360856..1a739866 100644 --- a/reference/html/spring-cloud-circuitbreaker.html +++ b/reference/html/spring-cloud-circuitbreaker.html @@ -245,6 +245,26 @@ the following documentation:

+
+

Some CircuitBreaker implementations such as Resilience4JCircuitBreaker call customize method every time CircuitBreaker#run is called. +It can be inefficient. In that case, you can use CircuitBreaker#once method. It is useful where calling customize many times doesn’t make sense, +for example, in case of consuming Resilience4j’s events.

+
+
+

The following example shows the way for each io.github.resilience4j.circuitbreaker.CircuitBreaker to consume events.

+
+
+
+
+
+
Customizer.once(circuitBreaker -> {
+  circuitBreaker.getEventPublisher()
+    .onStateTransition(event -> log.info("{}: {}", event.getCircuitBreakerName(), event.getStateTransition()));
+}, CircuitBreaker::getName)
+
+
+
+
diff --git a/reference/html/spring-cloud-commons.html b/reference/html/spring-cloud-commons.html index e3c5f136..b03c4292 100644 --- a/reference/html/spring-cloud-commons.html +++ b/reference/html/spring-cloud-commons.html @@ -1810,6 +1810,26 @@ the following documentation:

+
+

Some CircuitBreaker implementations such as Resilience4JCircuitBreaker call customize method every time CircuitBreaker#run is called. +It can be inefficient. In that case, you can use CircuitBreaker#once method. It is useful where calling customize many times doesn’t make sense, +for example, in case of consuming Resilience4j’s events.

+
+
+

The following example shows the way for each io.github.resilience4j.circuitbreaker.CircuitBreaker to consume events.

+
+
+
+
+
+
Customizer.once(circuitBreaker -> {
+  circuitBreaker.getEventPublisher()
+    .onStateTransition(event -> log.info("{}: {}", event.getCircuitBreakerName(), event.getStateTransition()));
+}, CircuitBreaker::getName)
+
+
+
+