From 2194c68fec6161de9ec9f6a262421e3a94e0fa01 Mon Sep 17 00:00:00 2001 From: Olga Semernitskaia Date: Tue, 5 Dec 2023 18:03:47 +0200 Subject: [PATCH] fix documentation for providing custom bean scenario --- riptide-spring-boot-autoconfigure/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/riptide-spring-boot-autoconfigure/README.md b/riptide-spring-boot-autoconfigure/README.md index 0a5b809f..0e680f2e 100644 --- a/riptide-spring-boot-autoconfigure/README.md +++ b/riptide-spring-boot-autoconfigure/README.md @@ -586,13 +586,13 @@ public ClientHttpMessageConverters exampleHttpMessageConverters() { } ``` -The following code can be used if cannot use your client name in the method name (e.g. your client name is `my-client`): +The following code can be used if your client name cannot be used in the method name (e.g. your client name is `my-client`): @Bean(name = "my-clientCircuitBreakerExecutorService") public ClientHttpMessageConverters httpMessageConverters() { return new ClientHttpMessageConverters(singletonList(new Jaxb2RootElementHttpMessageConverter())); } ``` -As you can see, any method name can be used in the second case. +As you can see, any method name can be used in the second example, since bean name is provided explicitly in the annotation. The following table shows all beans with their respective name (for the `example` client) and type: